AI agents invoke timeout to trigger actions in Malicious. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
seconds | string | — | Number of seconds to wait |
Parameters from the server's own tool schema.
This tool triggers a timed blocking operation on the server side. In a malicious context, it can be used for denial-of-service by tying up resources, causing timeouts in dependent systems, or as a stalling mechanism within agent workflows. The malicious server label elevates concern. Classified as Execute because it actively runs a wait/blocking operation whose effect depends on the argument supplied.
From the tool's definition 'Waits for specified number of seconds before responding' — deliberately induces delay/blocking behavior; server is explicitly labeled 'deliberately malicious MCP server for E2E testing purposes'
Attacks that exploit this kind of access
Waits for specified number of seconds before responding. It is categorised as a Execute tool in the Malicious MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
timeout accepts 1 parameter: seconds. The full parameter table on this page comes from the server's own tool schema.
Register the Malicious MCP server in PolicyLayer and add a rule for timeout: 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 Malicious. Nothing to install.
timeout 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 timeout 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 timeout. 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.
timeout is provided by the Malicious MCP server (malicious-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 →