Get LLM proxy statistics (requests, costs, latency)
AI agents call stockyard_proxy_stats to retrieve information from Stockyard MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing proxy statistics (requests, costs, latency metrics) and returns data for monitoring purposes. No data is modified, deleted, or executed. While it provides visibility into cost data, it only reads existing statistics without ability to move money or trigger financial transactions.
From the tool's definition Tool name 'stockyard_proxy_stats' and description 'Get LLM proxy statistics (requests, costs, latency)' indicate this retrieves monitoring/analytics data without modifying or executing operations. The verb 'Get' is explicitly read-only.
Attacks that exploit this kind of access
Get LLM proxy statistics (requests, costs, latency). It is categorised as a Read tool in the Stockyard MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stockyard MCP Server MCP server in PolicyLayer and add a rule for stockyard_proxy_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 Stockyard MCP Server. Nothing to install.
stockyard_proxy_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 stockyard_proxy_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 stockyard_proxy_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.
stockyard_proxy_stats is provided by the Stockyard MCP Server MCP server (stockyard-dev/stockyard-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 →