eu_parliament.meps.details
Retrieve the full profile and complete parliamentary membership history of a specific MEP by their numeric CODICT identifier. Returns the MEP's name, date of birth, gender, and all committee, political group, intergroup, and delegation memberships with start/end dates and roles. Use the meps.list...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/eu-parliament.meps.details.md
What eu_parliament.meps.details does on Apibase
AI agents call eu_parliament.meps.details to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mep_id | string | Yes | Numeric MEP identifier from the European Parliament CODICT system. Example: 197539 for Mikuláš Peksa. Obtain IDs via the meps.list tool. |
Parameters from the server's own tool schema.
Why eu_parliament.meps.details is rated Low
Tool only fetches public MEP profile data with no side effects.
From the tool's definition Retrieve the full profile and complete parliamentary membership history
Attacks that exploit this kind of access
The rule that runs eu_parliament.meps.details safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For eu_parliament.meps.details, this is the rule to start with:
eu_parliament.meps.details is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every eu_parliament.meps.details call is checked against it from then on.
Questions about eu_parliament.meps.details
Retrieve the full profile and complete parliamentary membership history of a specific MEP by their numeric CODICT identifier. Returns the MEP's name, date of birth, gender, and all committee, political group, intergroup, and delegation memberships with start/end dates and roles. Use the meps.list tool to look up MEP identifiers. Useful for understanding an MEP's committee responsibilities, political affiliations over time, and interparliamentary delegation work. Data source: European Parliament Open Data API v2 — CC BY 4.0, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
eu_parliament.meps.details accepts 1 parameter: mep_id. Required: mep_id. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for eu_parliament.meps.details: 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 Apibase. Nothing to install.
eu_parliament.meps.details 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 eu_parliament.meps.details 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 eu_parliament.meps.details. 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.
eu_parliament.meps.details is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue