add_timer
AI agents use add_timer to create or update resources in Xadeus-QQ-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xadeus-QQ-MCP environment.
The tool name and server context indicate it creates/schedules a timed task (a write operation that reversibly adds state). Without a detailed description, confidence is moderate. Severity is low because scheduling a timer is a bounded, reversible action with minimal blast radius—the worst case is an unwanted scheduled task that can be removed.
From the tool's definition Tool name 'add_timer' with context of 'timed tasks' in server description suggests creating or scheduling a timer/task, which modifies state by adding a new scheduled item.
Attacks that exploit this kind of access
add_timer. It is categorised as a Write tool in the Xadeus-QQ-MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xadeus-QQ- MCP server in PolicyLayer and add a rule for add_timer: 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 Xadeus-QQ-MCP. Nothing to install.
add_timer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_timer 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 add_timer. 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.
add_timer is provided by the Xadeus-QQ- MCP server (mouse114514/xadeus-qq-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 →