list_polls

List recorded parliamentary votes/polls (Abstimmungen) with their title and date. Optionally scope to a single legislative period via period_id (a parliament-period id). Returns most recent polls first.

Server Abgeordnetenwatch https://gateway.pipeworx.io/abgeordnetenwatch/mcp
Category Read
Risk class Low
Parameters 20 required

What list_polls does on Abgeordnetenwatch

AI agents call list_polls to retrieve information from Abgeordnetenwatch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
limit number Max results to return (default 10).
period_id number | string Optional parliament-period (legislature) id to filter polls.

Parameters from the server's own tool schema.

Why list_polls needs a policy

This tool retrieves historical parliamentary voting data without modifying, deleting, or executing any operations. It is a straightforward query operation that returns public legislative records. There is no capability to alter data, trigger external actions, or cause irreversible changes. The low severity reflects that misuse would only expose or organize already-public parliamentary information.

From the tool's definition Tool description states it 'List[s] recorded parliamentary votes/polls' and 'Returns most recent polls first'. The verb 'list' and the read-only nature of querying historical voting records indicate pure data retrieval with no side effects.

Questions about list_polls

What does the list_polls tool do? +

List recorded parliamentary votes/polls (Abstimmungen) with their title and date. Optionally scope to a single legislative period via period_id (a parliament-period id). Returns most recent polls first. It is categorised as a Read tool in the Abgeordnetenwatch MCP Server, which means it retrieves data without modifying state.

What parameters does list_polls accept? +

list_polls accepts 2 parameters: limit, period_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_polls? +

Register the Abgeordnetenwatch MCP server in PolicyLayer and add a rule for list_polls: 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 Abgeordnetenwatch. Nothing to install.

What risk level is list_polls? +

list_polls is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_polls? +

Yes. Add a rate_limit block to the list_polls 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.

How do I block list_polls completely? +

Set action: deny in the PolicyLayer policy for list_polls. 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.

What MCP server provides list_polls? +

list_polls is provided by the Abgeordnetenwatch MCP server (https://gateway.pipeworx.io/abgeordnetenwatch/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.