Get detailed execution metrics for specific or all tools.
AI agents call get_tool_metrics to retrieve information from Reversecore_MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and returns metrics data without creating, modifying, deleting, or executing any actions. The blast radius is minimal since the tool only exposes performance/usage statistics, not sensitive binary analysis results or system state modifications.
From the tool's definition The tool name and description describe only retrieval of metrics: 'Get detailed execution metrics for specific or all tools' is a query operation with no side effects. It retrieves pre-computed or logged data about tool execution.
Attacks that exploit this kind of access
Get detailed execution metrics for specific or all tools. It is categorised as a Read tool in the Reversecore_MCP MCP Server, which means it retrieves data without modifying state.
Register the Reversecore_ MCP server in PolicyLayer and add a rule for get_tool_metrics: 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 Reversecore_MCP. Nothing to install.
get_tool_metrics 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_tool_metrics 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_tool_metrics. 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_tool_metrics is provided by the Reversecore_ MCP server (sjkim1127/reversecore_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 →