extract_structured
AI agents call extract_structured to retrieve information from Metis Public Health without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, confidence is reduced. However, the verb 'extract' strongly implies data retrieval from the indexed PDF library (consistent with Metis's stated function to 'answer from the user's own indexed PDF library'). No evidence of side effects, code execution, or data modification. Classified as Read with low-to-medium confidence due to missing details.
From the tool's definition Tool name 'extract_structured' suggests extracting data in a structured format; no description provided. Context from sibling tools (add_glossary_term, add_journal_entry, add_memory_entry, etc.) shows this server is designed for local document indexing and…
Attacks that exploit this kind of access
extract_structured. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for extract_structured: 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.
extract_structured is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the extract_structured 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 extract_structured. 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.
extract_structured 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 →