get_agent_context

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/get-agent-context.md

WHAT IT DOES

What get_agent_context does on Metis Public Health

AI agents call get_agent_context 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 get_agent_context is rated Low

Although the tool description is empty, the naming convention ('get_*'), server context (code analysis platform), and sibling tools all indicate this retrieves or queries agent context data without modifying state. This is a Read operation. Confidence is slightly reduced due to the missing description, but the contextual evidence is strong.

From the tool's definition Tool name 'get_agent_context' suggests retrieval of context information. The server's stated purpose is to 'Analyze any codebase — get architecture, file roles, execution flows, and agent context', positioning this as a read/query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_agent_context 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 get_agent_context, this is the rule to start with:

get_agent_context Allowed

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

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 get_agent_context call is checked against it from then on.

FAQ

Questions about get_agent_context

What does the get_agent_context tool do? +

get_agent_context 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 get_agent_context? +

Register the Metis Public Health MCP server in PolicyLayer and add a rule for get_agent_context: 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 get_agent_context? +

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

Can I rate-limit get_agent_context? +

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

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

get_agent_context 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

get_agent on 0rca Dojo MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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