AI agents call get_performance_metrics to retrieve information from Mnemex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metrics (likely CPU, memory, latency, or similar performance data) for monitoring purposes. It performs a read-only query of existing performance state with no capability to modify data, trigger external operations, or cause destructive effects. The low severity reflects minimal blast radius if misused—an AI agent querying performance metrics poses negligible risk.
From the tool's definition Tool name 'get_performance_metrics' and description 'Get current performance metrics' indicate a retrieval operation that queries system performance data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_performance_metrics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mnemex, and nothing reaches the server without passing your rules. This is the rule we recommend for get_performance_metrics:
{
"version": "1",
"default": "deny",
"tools": {
"get_performance_metrics": {}
}
}get_performance_metrics 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 current performance metrics. It is categorised as a Read tool in the Mnemex MCP Server, which means it retrieves data without modifying state.
Register the Mnemex MCP server in PolicyLayer and add a rule for get_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 Mnemex. Nothing to install.
get_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 get_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 get_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.
get_performance_metrics is provided by the Mnemex MCP server (prefrontal-systems/cortexgraph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Mnemex tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Mnemex tools catalogued and risk-classified — across an index of 42,500+ MCP servers.