eurlex.legislation.detail
Retrieve full metadata for a specific EU legal act identified by its CELEX number from EUR-Lex Cellar. Returns CELEX identifier, publication date, English title, in-force status, Cellar URI, and direct EUR-Lex URL. CELEX examples: "32024R1689" (EU AI Act), "32016R0679" (GDPR), "32023R1115" (EU De...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/eurlex.legislation.detail.md
What eurlex.legislation.detail does on Apibase
AI agents call eurlex.legislation.detail 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 |
|---|---|---|---|
celex | string | Yes | CELEX identifier of the EU legal act to retrieve (e.g. "32024R1689" for the EU AI Act, "32016R0679" for GDPR, "32023R1115" for EU Deforestation Regulation). For |
Parameters from the server's own tool schema.
Why eurlex.legislation.detail is rated Low
Tool queries and retrieves public EU legislation metadata without modifying or executing anything.
From the tool's definition Retrieve full metadata for a specific EU legal act identified by its CELEX number
Attacks that exploit this kind of access
The rule that runs eurlex.legislation.detail 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 eurlex.legislation.detail, this is the rule to start with:
eurlex.legislation.detail 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 eurlex.legislation.detail call is checked against it from then on.
Questions about eurlex.legislation.detail
Retrieve full metadata for a specific EU legal act identified by its CELEX number from EUR-Lex Cellar. Returns CELEX identifier, publication date, English title, in-force status, Cellar URI, and direct EUR-Lex URL. CELEX examples: "32024R1689" (EU AI Act), "32016R0679" (GDPR), "32023R1115" (EU Deforestation Regulation), "32022R2065" (Digital Services Act), "32020R0852" (EU Taxonomy Regulation). CELEX format: sector digit (3 = secondary EU law) + 4-digit year + type letter (R=Regulation, L=Directive, D=Decision) + sequential number. Returns found=false if the CELEX number does not exist in EUR-Lex Cellar. Data source: EU Publications Office EUR-Lex Cellar — official EU law repository, no auth required, open access. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
eurlex.legislation.detail accepts 1 parameter: celex. Required: celex. 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 eurlex.legislation.detail: 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.
eurlex.legislation.detail 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 eurlex.legislation.detail 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 eurlex.legislation.detail. 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.
eurlex.legislation.detail 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