srgssr_polis_get_votations
AI agents call srgssr_polis_get_votations to retrieve information from Pypi:srgssr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about Swiss votations (public voting events), which is historical public data with no mutation or side effects. The 'get_' prefix and alignment with other read-only tools on the server indicate a query/retrieval operation. No financial transactions, destructive operations, or code execution is involved.
From the tool's definition Tool name 'srgssr_polis_get_votations' indicates a getter/retrieval function following the 'get_' naming pattern. Sibling tools on the server (srgssr_polis_get_elections, srgssr_polis_get_votation_results) are all read-only query operations.
Attacks that exploit this kind of access
srgssr_polis_get_votations. It is categorised as a Read tool in the Pypi:srgssr MCP Server, which means it retrieves data without modifying state.
Register the Pypi:srgssr MCP server in PolicyLayer and add a rule for srgssr_polis_get_votations: 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:srgssr. Nothing to install.
srgssr_polis_get_votations 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 srgssr_polis_get_votations 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 srgssr_polis_get_votations. 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.
srgssr_polis_get_votations is provided by the Pypi:srgssr MCP server (malkreide/srgssr-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 →