record_dataset_treatment
AI agents use record_dataset_treatment to create or update resources in Metis Public Health — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Metis Public Health environment.
The name implies creating or updating a record of how a dataset was treated or processed. With sibling tools like 'add_journal_entry', 'add_memory_entry', and 'add_tracked_file', this server appears oriented toward writing/recording research metadata. Empty description lowers confidence significantly.
From the tool's definition Tool name 'record_dataset_treatment' suggests writing/recording treatment information about a dataset; description is empty and uninformative.
Attacks that exploit this kind of access
record_dataset_treatment. It is categorised as a Write tool in the Metis Public Health MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for record_dataset_treatment: 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.
record_dataset_treatment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the record_dataset_treatment 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 record_dataset_treatment. 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.
record_dataset_treatment 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 →