Low Risk

metrics_summary

Gets comprehensive metrics summary for monitoring.

How to control metrics_summary ↓

What metrics_summary does on Open Stocks MCP

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

Low Risk

Why metrics_summary needs a policy

This tool retrieves and queries financial metrics data for display/monitoring purposes. It does not create, modify, delete, or execute transactions. While the server offers trading capabilities, this specific tool is strictly informational. The low severity reflects that misuse would only expose data already available to the authenticated user, with no ability to alter account state or execute trades.

From the tool's definition Tool name 'metrics_summary' and description 'Gets comprehensive metrics summary for monitoring' indicate data retrieval only. The verb 'Gets' and the purpose of 'monitoring' (passive observation) confirm read-only behavior with no side effects.

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

How to control metrics_summary

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

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

metrics_summary 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 Open Stocks MCP — 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 metrics_summary

What does the metrics_summary tool do? +

Gets comprehensive metrics summary for monitoring. It is categorised as a Read tool in the Open Stocks MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on metrics_summary? +

Register the Open Stocks MCP server in PolicyLayer and add a rule for metrics_summary: 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 Open Stocks MCP. Nothing to install.

What risk level is metrics_summary? +

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

Can I rate-limit metrics_summary? +

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

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

metrics_summary is provided by the Open Stocks MCP server (open-agent-tools/open-stocks-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Open Stocks MCP tool call.

Start from Open Stocks MCP, 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.

152 Open Stocks MCP 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.