register_code_artifact
AI agents use register_code_artifact 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 indicates a write operation that creates or modifies a record (registration) for code artifacts. Without a description, confidence is reduced, but the 'register_' prefix typically implies recording/storing data reversibly. Given the context of a research companion system with features like 'add_journal_entry' and 'add_memory_entry' (both Write operations), this likely creates a new artifact record.
From the tool's definition Tool name 'register_code_artifact' suggests creating or recording a code artifact entry in a system.
Attacks that exploit this kind of access
register_code_artifact. 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 register_code_artifact: 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.
register_code_artifact 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 register_code_artifact 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 register_code_artifact. 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.
register_code_artifact 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 →