Get performance statistics for CoD vs CoT approaches
AI agents call get_performance_stats to retrieve information from Chain of Draft (CoD) MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns comparative performance data between Chain of Draft and Chain of Thought reasoning approaches. It has no capability to modify, execute, delete, or commit financial transactions. It is purely informational and read-only in nature, making it a Read category tool with low severity risk.
From the tool's definition Tool name 'get_performance_stats' and description 'Get performance statistics for CoD vs CoT approaches' indicate data retrieval only. The verb 'Get' combined with 'statistics' shows a query/fetch operation with no modifications, executions, or side effects.
Documented attack patterns abuse exactly the kind of access get_performance_stats gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Chain of Draft (CoD) MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_performance_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_performance_stats": {}
}
} get_performance_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get performance statistics for CoD vs CoT approaches. It is categorised as a Read tool in the Chain of Draft (CoD) MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Chain of Draft (CoD) MCP Server MCP server in PolicyLayer and add a rule for get_performance_stats: 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 Chain of Draft (CoD) MCP Server. Nothing to install.
get_performance_stats 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 get_performance_stats 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 get_performance_stats. 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.
get_performance_stats is provided by the Chain of Draft (CoD) MCP Server MCP server (stat-guy/chain-of-draft). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chain of Draft (CoD) MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Chain of Draft (CoD) MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.