Get performance metrics including database size, query times, and resource usage
AI agents call get_performance_status to retrieve information from In Memoria without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system performance metrics (database size, query times, resource usage) without side effects. It is purely informational, returning status data about the system's operational state. No data is created, modified, deleted, or executed—only queried. This is a standard read operation typical of health/monitoring endpoints.
From the tool's definition Tool name 'get_performance_status' and description 'Get performance metrics including database size, query times, and resource usage' indicate retrieval of monitoring/observability data with no modification capability.
Documented attack patterns abuse exactly the kind of access get_performance_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and In Memoria, and nothing reaches the server without passing your rules. This is the rule we recommend for get_performance_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_performance_status": {}
}
}get_performance_status 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 metrics including database size, query times, and resource usage. It is categorised as a Read tool in the In Memoria MCP Server, which means it retrieves data without modifying state.
Register the In Memoria MCP server in PolicyLayer and add a rule for get_performance_status: 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 In Memoria. Nothing to install.
get_performance_status 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_status 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_status. 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_status is provided by the In Memoria MCP server (pi22by7/in-memoria). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 14 In Memoria tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
14 In Memoria tools catalogued and risk-classified — across an index of 42,500+ MCP servers.