Low Risk

get_server_metrics

Get server performance metrics.

How to control get_server_metrics ↓

What get_server_metrics does on MCP Project Orchestrator

AI agents call get_server_metrics to retrieve information from MCP Project Orchestrator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_server_metrics needs a policy

This tool retrieves monitoring/metrics data from servers. It is a read-only query operation with no capability to modify infrastructure, execute commands, or cause destructive changes. The blast radius of misuse is minimal—an agent could at most view performance statistics, which poses no direct risk to systems or data integrity.

From the tool's definition Tool name 'get_server_metrics' and description 'Get server performance metrics' indicate a retrieval operation that queries performance data without modifying, executing code, or causing side effects.

Documented attack patterns abuse exactly the kind of access get_server_metrics gives an agent:

How to control get_server_metrics

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Project Orchestrator, and nothing reaches the server without passing your rules. This is the rule we recommend for get_server_metrics:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_server_metrics": {}
  }
}

get_server_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register MCP Project Orchestrator — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_server_metrics

What does the get_server_metrics tool do? +

Get server performance metrics. It is categorised as a Read tool in the MCP Project Orchestrator MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_server_metrics? +

Register the MCP Project Orchestrator MCP server in PolicyLayer and add a rule for get_server_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 Project Orchestrator. Nothing to install.

What risk level is get_server_metrics? +

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

Can I rate-limit get_server_metrics? +

Yes. Add a rate_limit block to the get_server_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_server_metrics completely? +

Set action: deny in the PolicyLayer policy for get_server_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_server_metrics? +

get_server_metrics is provided by the MCP Project Orchestrator MCP server (sparesparrow/mcp-project-orchestrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Project Orchestrator tool call.

Start from MCP Project Orchestrator, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

15 MCP Project Orchestrator tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.