probe_tool_result

A read tool on the Metis Public Health MCP server.

SERVERMetis Public Health SOURCEsveritg/metis_ph

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/sveritg-metis-ph/probe-tool-result.md

WHAT IT DOES

What probe_tool_result does on Metis Public Health

AI agents call probe_tool_result to retrieve information from Metis Public Health without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why probe_tool_result is rated Low

Even though probe_tool_result only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs probe_tool_result safely

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

probe_tool_result Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every probe_tool_result call is checked against it from then on.

FAQ

Questions about probe_tool_result

What does the probe_tool_result tool do? +

probe_tool_result is a read tool on the Metis Public Health MCP server. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on probe_tool_result? +

Register the Metis Public Health MCP server in PolicyLayer and add a rule for probe_tool_result: 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 Metis Public Health. Nothing to install.

What risk level is probe_tool_result? +

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

Can I rate-limit probe_tool_result? +

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

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

probe_tool_result is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Metis Public Health, and thousands of servers like it.

This server

All 277 Metis Public Health tools →

Across the catalogue

The MCP Attack Database →

Guides

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