lobbywatch_list_interessenbindungen
AI agents call lobbywatch_list_interessenbindungen 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 lists transparency-related data (interest bindings/conflicts of interest) from the Lobbywatch database without modifying, executing operations, or causing irreversible changes. Despite empty description, the naming pattern and server context clearly indicate a read operation.
From the tool's definition Tool name 'lobbywatch_list_interessenbindungen' (list interest bindings/conflicts of interest) and server context showing read-only access to Swiss parliamentarians' transparency data (conflicts of interest, lobby groups, access badges).
Attacks that exploit this kind of access
lobbywatch_list_interessenbindungen. 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_list_interessenbindungen: 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_list_interessenbindungen 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_list_interessenbindungen 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_list_interessenbindungen. 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_list_interessenbindungen 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 →