Return current dump cache status without forcing a refresh.
AI agents call lobbywatch_dump_status to retrieve information from Pypi:lobbywatch 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 status information about an internal cache state. It is a passive read operation with no side effects, no data modification, and no external operations triggered. The low severity reflects minimal blast radius—misuse would only expose cache metadata, not trigger unintended data changes or operations.
From the tool's definition Tool name 'lobbywatch_dump_status' and description 'Return current dump cache status without forcing a refresh' indicate querying/checking the status of cached data. No modification, deletion, execution of external commands, or financial transactions occur.
Attacks that exploit this kind of access
Return current dump cache status without forcing a refresh. It is categorised as a Read tool in the Pypi:lobbywatch MCP Server, which means it retrieves data without modifying state.
Register the Pypi:lobbywatch MCP server in PolicyLayer and add a rule for lobbywatch_dump_status: 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:lobbywatch. Nothing to install.
lobbywatch_dump_status 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 lobbywatch_dump_status 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 lobbywatch_dump_status. 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.
lobbywatch_dump_status is provided by the Pypi:lobbywatch MCP server (pypi:lobbywatch-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 →