get_memory_stats

Get optimization statistics and performance metrics

SERVERClaude MCP Server Ecosystem SOURCEcoder-rl/claude_mcpserver_dev1

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coder-rl-claude-mcpserver-dev1/get-memory-stats.md

WHAT IT DOES

What get_memory_stats does on Claude MCP Server Ecosystem

AI agents call get_memory_stats to retrieve information from Claude MCP Server Ecosystem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_memory_stats is rated Low

This tool retrieves statistics and metrics from an in-memory system without altering state, executing commands, or affecting data. It is purely informational (Read category). Severity is low because exposure of performance metrics poses minimal risk—the data is typically non-sensitive operational information used for monitoring purposes.

From the tool's definition Tool name 'get_memory_stats' and description 'Get optimization statistics and performance metrics' indicate retrieval of monitoring/observability data with no modification or execution of external operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_memory_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude MCP Server Ecosystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_memory_stats, this is the rule to start with:

get_memory_stats Allowed

get_memory_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_memory_stats": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claude MCP Server Ecosystem, apply this rule, and every get_memory_stats call is checked against it from then on.

FAQ

Questions about get_memory_stats

What does the get_memory_stats tool do? +

Get optimization statistics and performance metrics. It is categorised as a Read tool in the Claude MCP Server Ecosystem MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_memory_stats? +

Register the Claude MCP Server Ecosystem MCP server in PolicyLayer and add a rule for get_memory_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 Claude MCP Server Ecosystem. Nothing to install.

What risk level is get_memory_stats? +

get_memory_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_memory_stats? +

Yes. Add a rate_limit block to the get_memory_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.

How do I block get_memory_stats completely? +

Set action: deny in the PolicyLayer policy for get_memory_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.

What MCP server provides get_memory_stats? +

get_memory_stats is provided by the Claude MCP Server Ecosystem MCP server (coder-rl/claude_mcpserver_dev1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude MCP Server Ecosystem, and thousands of servers like it.

This server

All 229 Claude MCP Server Ecosystem tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →