start_span
AI agents call start_span as a supporting operation in Metis Public Health workflows.
The description is entirely empty, making it impossible to determine what this tool does from its description. The name 'start_span' could refer to starting a tracing/telemetry span (observability instrumentation), which would be a low-risk read/other operation. Given the context of a public health research server with PDF indexing and specialist agents, it may relate to text span marking or tracing.
From the tool's definition Tool name is 'start_span' and description is empty or uninformative.
Attacks that exploit this kind of access
start_span. It is categorised as a Other tool in the Metis Public Health MCP Server, which means it performs auxiliary operations.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for start_span: 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.
start_span is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the start_span 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.
Set action: deny in the PolicyLayer policy for start_span. 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.
start_span 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →