srgssr_polis_get_elections
AI agents call srgssr_polis_get_elections 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 election data from a public Swiss broadcasting API. No modification, deletion, execution, or financial operations are involved. It is a straightforward data retrieval endpoint, classified as Read. Confidence is slightly reduced (0.85) due to the missing description, but strong inference from naming convention and sibling tools mitigates this.
From the tool's definition Tool name 'srgssr_polis_get_elections' follows the pattern of sibling tools (srgssr_polis_get_votations, srgssr_polis_get_votation_results) which query public SRG SSR APIs for historical metadata (Swiss elections since 1900).
Attacks that exploit this kind of access
srgssr_polis_get_elections. 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_elections: 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_elections 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_elections 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_elections. 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_elections 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 →