Get statistics about loaded mapping files
AI agents call get_mapping_statistics to retrieve information from DailyMed MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports statistics about mapping files—a passive query operation with no side effects, data modification, code execution, or irreversible actions. It falls clearly into the Read category. The severity is low because statistics queries have minimal blast radius and cannot be misused to cause harm to data, systems, or financial transactions.
From the tool's definition Tool name 'get_mapping_statistics' and description 'Get statistics about loaded mapping files' indicate a retrieval operation that queries existing data without modification. The action is read-only and returns informational metrics.
Attacks that exploit this kind of access
Get statistics about loaded mapping files. It is categorised as a Read tool in the DailyMed MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DailyMed MCP Server MCP server in PolicyLayer and add a rule for get_mapping_statistics: 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 DailyMed MCP Server. Nothing to install.
get_mapping_statistics 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 get_mapping_statistics 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 get_mapping_statistics. 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.
get_mapping_statistics is provided by the DailyMed MCP Server MCP server (rowanerasmus/dailymed-mcp-server). 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 →