Get memory (RAM and swap) usage statistics.
AI agents call get_memory_info to retrieve information from System Monitor MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system memory statistics without modifying, executing code, deleting data, or affecting system state. It is a straightforward information query operation analogous to 'get' or 'fetch' operations. Low severity because even if misused by an agent, memory information disclosure poses minimal risk.
From the tool's definition Tool name 'get_memory_info' and description 'Get memory (RAM and swap) usage statistics' indicate a retrieval operation with no side effects. The verb 'get' combined with the nature of the operation (querying usage statistics) confirms read-only functionality.
Attacks that exploit this kind of access
Get memory (RAM and swap) usage statistics. It is categorised as a Read tool in the System Monitor MCP Server MCP Server, which means it retrieves data without modifying state.
Register the System Monitor MCP Server MCP server in PolicyLayer and add a rule for get_memory_info: 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 System Monitor MCP Server. Nothing to install.
get_memory_info 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_memory_info 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_memory_info. 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_memory_info is provided by the System Monitor MCP Server MCP server (praveert/cord). 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 →