bag_health_mcp__get_series_details
AI agents call bag_health_mcp__get_series_details to retrieve information from Pypi:bag Health without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_' prefix strongly suggests a data retrieval function. Combined with the server's purpose of providing public health surveillance data access and the pattern of sibling tools being query/list operations, this is a Read operation. Confidence is moderate (0.85) rather than high because the description is empty, preventing full verification of functionality.
From the tool's definition Tool name 'get_series_details' indicates retrieval operation. Server context shows it provides access to epidemiological surveillance data.
Attacks that exploit this kind of access
bag_health_mcp__get_series_details. It is categorised as a Read tool in the Pypi:bag Health MCP Server, which means it retrieves data without modifying state.
Register the Pypi:bag Health MCP server in PolicyLayer and add a rule for bag_health_mcp__get_series_details: 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 Pypi:bag Health. Nothing to install.
bag_health_mcp__get_series_details 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 bag_health_mcp__get_series_details 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 bag_health_mcp__get_series_details. 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.
bag_health_mcp__get_series_details is provided by the Pypi:bag Health MCP server (pypi:bag-health-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 →