Hello, I've been trying to connect to Composio through Openclaw and my bot is telling me about the plugin issue below. I'm currently using the workaround proposed by my openclaw bot at the bottom of my message below. The workaround was working fine initially, but now I keep getting the API rate limit warning from Composio. Any tips on how to proceed? I'm not technical and this is my first time using Openclaw and MCPs. Thanks. _____ This is the problem: The Composio MCP server is working perfectly, but the OpenClaw Composio plugin isn't properly injecting these tools into my runtime. The Composio MCP server IS working and responding correctly! I can see all 7 tools listed in the response: 1. COMPOSIO_MANAGE_CONNECTIONS ✓ 2. COMPOSIO_MULTI_EXECUTE_TOOL ✓ 3. COMPOSIO_REMOTE_BASH_TOOL ✓ 4. COMPOSIO_REMOTE_WORKBENCH ✓ 5. COMPOSIO_SEARCH_TOOLS ✓ 6. COMPOSIO_WAIT_FOR_CONNECTIONS ✓ 7. COMPOSIO_GET_TOOL_SCHEMAS ✓ This suggests: 1. The plugin is installed and can connect to the MCP server 2. But there's a gap in how it registers the tools with the OpenClaw agent ─── At this point we've hit a technical limitation that's beyond standard troubleshooting: The Composio MCP server is available and functional, but the OpenClaw plugin architecture isn't exposing those tools to me in a way I can call them directly. Workaround: Use the MCP server directly — I could make raw HTTP calls to https://connect.composio.dev/mcp to create connections and execute tools, but that's not ideal since the plugin is supposed to handle that

Hey @Sid, sorry for the delayed response. The rate limit could be due to our recent issue with tool-router's search. You can check the status and the effect here: https://status.composio.dev/cmmlm09ed000rap0qmb9l23kp Let me know if this helps?