Scan content for PII patterns and classify sensitivity level.
AI agents call check_data_safety 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.
This tool retrieves information about data (scans for PII patterns) and assigns a classification level, which is a read-only analysis operation with no side effects. It does not create, modify, delete, or execute code/commands. The data being analyzed remains unchanged after the scan. While the output may reveal sensitive information about content, the tool itself performs only non-destructive inspection.
From the tool's definition Tool name 'check_data_safety' and description 'Scan content for PII patterns and classify sensitivity level' indicates the tool performs pattern matching and classification analysis on content without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Scan content for PII patterns and classify sensitivity level. 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 check_data_safety: 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.
check_data_safety 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 check_data_safety 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 check_data_safety. 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.
check_data_safety 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 →