get_metrics

Returns performance metrics about server operations.

SERVERMCP Filesystem Server SOURCEa-niranjan/mcp-filesystem

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/a-niranjan-mcp-filesystem/get-metrics.md

WHAT IT DOES

What get_metrics does on MCP Filesystem Server

AI agents call get_metrics to retrieve information from MCP Filesystem Server 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_metrics is rated Low

This tool queries and returns performance data without modifying, executing code, deleting, or creating resources. It is a straightforward read operation that retrieves monitoring information, posing minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'get_metrics' and description 'Returns performance metrics about server operations' indicate a retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_metrics safely

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

get_metrics Allowed

get_metrics 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_metrics": {}
  }
}

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

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

FAQ

Questions about get_metrics

What does the get_metrics tool do? +

Returns performance metrics about server operations. It is categorised as a Read tool in the MCP Filesystem Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_metrics? +

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

What risk level is get_metrics? +

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

Can I rate-limit get_metrics? +

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

How do I block get_metrics completely? +

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

What MCP server provides get_metrics? +

get_metrics is provided by the MCP Filesystem Server MCP server (a-niranjan/mcp-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

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

This server

All 17 MCP Filesystem Server tools →

Across the catalogue

get_customer_metrics on 08-AI-Business-Agent →get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server → The MCP Attack Database →

Guides

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