mcp_performance_metrics
Get detailed performance metrics and statistics
This record as markdown: /tools/ae/mcp-performance-metrics.md
What mcp_performance_metrics does on Ae
AI agents call mcp_performance_metrics to retrieve information from Ae without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mcp_performance_metrics is rated Low
The tool fetches performance metrics and statistics, which is a read-only operation. No data is created, modified, or deleted. Low severity as misuse would only expose internal performance data.
From the tool's definition 'Get detailed performance metrics and statistics' — purely retrieves data with no side effects
Attacks that exploit this kind of access
The rule that runs mcp_performance_metrics safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ae, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_performance_metrics, this is the rule to start with:
mcp_performance_metrics is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ae, apply this rule, and every mcp_performance_metrics call is checked against it from then on.
Questions about mcp_performance_metrics
Get detailed performance metrics and statistics. It is categorised as a Read tool in the Ae MCP Server, which means it retrieves data without modifying state.
Register the Ae MCP server in PolicyLayer and add a rule for mcp_performance_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 Ae. Nothing to install.
mcp_performance_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 mcp_performance_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 mcp_performance_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.
mcp_performance_metrics is provided by the Ae MCP server (ae-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ae, and thousands of servers like it.
This server
Across the catalogue