lobbywatch_get_ranking
AI agents call lobbywatch_get_ranking 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.
Despite the description being empty, the naming convention 'get_ranking' combined with the server's overall read-only transparency database purpose indicates this tool retrieves ranking information without modifying data or triggering external operations. This falls squarely into the Read category with low severity given the non-sensitive nature of public parliamentary transparency data.
From the tool's definition Tool name 'lobbywatch_get_ranking' suggests retrieval of ranking data. The server provides read-only access to Swiss parliamentary transparency data (conflicts of interest, lobby groups, badges, scores).
Attacks that exploit this kind of access
lobbywatch_get_ranking. 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_get_ranking: 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_get_ranking 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_get_ranking 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_get_ranking. 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_get_ranking 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 →