lobbywatch_refresh_dump
AI agents invoke lobbywatch_refresh_dump to trigger actions in Pypi:lobbywatch. 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.
The name 'refresh_dump' suggests triggering a data refresh or regeneration of a database dump, which is an external operation with side effects. In the context of the Lobbywatch.ch database server, this likely re-fetches or re-exports the underlying dataset. Because the description is empty, confidence is low, but 'refresh' implies an active operation (Execute) rather than a simple read.
From the tool's definition Tool name contains 'refresh_dump' — description is empty and uninformative, so classification relies solely on the name.
Attacks that exploit this kind of access
lobbywatch_refresh_dump. It is categorised as a Execute tool in the Pypi:lobbywatch MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Pypi:lobbywatch MCP server in PolicyLayer and add a rule for lobbywatch_refresh_dump: 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_refresh_dump 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 lobbywatch_refresh_dump 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_refresh_dump. 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_refresh_dump 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 →