register_data_dictionary
AI agents use register_data_dictionary 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 'register' verb typically means to record or store a new entity. In the context of a local-first research companion that indexes and manages user data, registering a data dictionary would create or update metadata definitions. This is reversible (can be unregistered/modified), so Write rather than Destructive.
From the tool's definition Tool name 'register_data_dictionary' indicates data structure registration/creation. No description provided, so classification is inferred from the verb 'register' and context of sibling tools (add_glossary_term, add_journal_entry, add_memory_entry,…
Attacks that exploit this kind of access
register_data_dictionary. 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_data_dictionary: 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_data_dictionary 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_data_dictionary 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_data_dictionary. 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_data_dictionary 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 →