List all configured timer tasks.
AI agents call list_timers to retrieve information from Xadeus-QQ-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing timer configuration data without modifying, deleting, or executing any timers. It is a read-only information gathering operation with minimal security impact.
From the tool's definition Tool name 'list_timers' and description 'List all configured timer tasks' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List all configured timer tasks. It is categorised as a Read tool in the Xadeus-QQ-MCP MCP Server, which means it retrieves data without modifying state.
Register the Xadeus-QQ- MCP server in PolicyLayer and add a rule for list_timers: 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.
list_timers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_timers 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 list_timers. 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.
list_timers 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 →