List all NHI coverage rules available in the local database.
AI agents call list_nhi_coverage_rules to retrieve information from Pharmacy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns existing data (NHI coverage rules) from a local database without modifying, deleting, executing code, or creating financial transactions. It is purely informational and safe to call with any arguments. The blast radius of misuse is minimal—worst case, an AI agent learns about pharmaceutical coverage policies.
From the tool's definition Tool name includes 'list' and description states 'List all NHI coverage rules available in the local database' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all NHI coverage rules available in the local database. It is categorised as a Read tool in the Pharmacy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Pharmacy MCP Server MCP server in PolicyLayer and add a rule for list_nhi_coverage_rules: 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 Pharmacy MCP Server. Nothing to install.
list_nhi_coverage_rules 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 list_nhi_coverage_rules 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 list_nhi_coverage_rules. 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.
list_nhi_coverage_rules is provided by the Pharmacy MCP Server MCP server (u9401066/pharmacy-mcp). 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 →