Add a topic to track for new publications.
AI agents use add_user_topic 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.
This tool creates or registers a new topic entry in the user's tracking system for monitoring publications. It modifies the user's stored preferences/topics reversibly—users can remove or change tracked topics. It has no destructive, financial, or execute characteristics. The blast radius is minimal: worst case, irrelevant publication alerts are generated.
From the tool's definition Tool name 'add_user_topic' and description 'Add a topic to track for new publications' indicate creation of new tracking data. The verb 'Add' and the action of creating a topic entry are characteristic of Write operations.
Attacks that exploit this kind of access
Add a topic to track for new publications. 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 add_user_topic: 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.
add_user_topic 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 add_user_topic 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 add_user_topic. 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.
add_user_topic 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 →