dhis2_query
A execute tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/dhis2-query.md
What dhis2_query does on Metis Public Health
AI agents invoke dhis2_query to trigger actions in Metis Public Health. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why dhis2_query is rated High
DHIS2 is a health information management platform. A 'query' tool could range from read-only data retrieval to executing arbitrary queries that may modify or extract sensitive health data. Given the public health server context and the potential for handling sensitive patient/population health data, the severity is elevated.
From the tool's definition Tool name 'dhis2_query' suggests querying a DHIS2 (District Health Information Software 2) system. Description is empty, providing no further detail.
Attacks that exploit this kind of access
The rule that runs dhis2_query safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dhis2_query, this is the rule to start with:
dhis2_query stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every dhis2_query call is checked against it from then on.
Questions about dhis2_query
dhis2_query is a execute tool on the Metis Public Health MCP server. It is categorised as a Execute tool in the Metis Public Health MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for dhis2_query: 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_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dhis2_query 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_query. 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_query 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.
More on Metis Public Health, and thousands of servers like it.
Across the catalogue