AI agents invoke chat_with_agent to trigger actions in Smallest. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool actively triggers a real-time WebSocket connection and sends messages to a published AI agent, causing external operations to occur. It's not a passive read — it initiates a live interaction session with an external service, making Execute the most appropriate category.
From the tool's definition Hold a TEXT conversation with a published agent over the realtime chat WebSocket (mode=chat)
Attacks that exploit this kind of access
Hold a TEXT conversation with a published agent over the realtime chat WebSocket (mode=chat) —. It is categorised as a Execute tool in the Smallest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Smallest MCP server in PolicyLayer and add a rule for chat_with_agent: 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 Smallest. Nothing to install.
chat_with_agent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the chat_with_agent 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 chat_with_agent. 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.
chat_with_agent is provided by the Smallest MCP server (@developer-smallestai/smallest-mcp-server). 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 →