dhis2_metadata
AI agents call dhis2_metadata 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.
Without a description, classification relies on the tool name and context. 'Metadata' operations typically retrieve configuration or structural information rather than create, modify, or destroy it. However, confidence is reduced due to the empty description; if this tool actually modifies DHIS2 system configuration, it could be categorized as Write.
From the tool's definition Tool name 'dhis2_metadata' suggests querying metadata from DHIS2 (District Health Information Software System), a common public health data platform. The naming convention 'dhis2_' prefix with 'metadata' indicates a retrieval operation rather than mutation.
Attacks that exploit this kind of access
dhis2_metadata. 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 dhis2_metadata: 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.
dhis2_metadata 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 dhis2_metadata 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 dhis2_metadata. 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.
dhis2_metadata 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 →