AI agents call clawd_gateway as a supporting operation in Clawd workflows.
The description is empty, making classification highly uncertain. Based solely on the name 'clawd_gateway' and the server context referencing communication gateways for WhatsApp and Discord, this tool likely manages or interfaces with messaging platform gateways. Without more information, it could be Read, Write, or Execute.
From the tool's definition Tool name is 'clawd_gateway' with an empty description. The server context mentions 'communication gateways across platforms like WhatsApp and Discord'.
Attacks that exploit this kind of access
clawd_gateway. It is categorised as a Other tool in the Clawd MCP Server, which means it performs auxiliary operations.
Register the Clawd MCP server in PolicyLayer and add a rule for clawd_gateway: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Clawd. Nothing to install.
clawd_gateway is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the clawd_gateway rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for clawd_gateway. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
clawd_gateway is provided by the Clawd MCP server (sandraschi/openclaw-molt-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →