eurlex.legislation.search
Search the official EUR-Lex Cellar SPARQL endpoint for EU legislative acts by keyword in English titles. Returns matching regulations, directives, and decisions with CELEX identifier, date, English title, in-force status, Cellar URI, and a direct EUR-Lex URL. Examples: keyword="artificial intelli...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/eurlex.legislation.search.md
What eurlex.legislation.search does on Apibase
AI agents call eurlex.legislation.search 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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return (1–20, default 10) |
keyword | string | Yes | English keyword to search for in EU legislation titles (e.g. "artificial intelligence", "GDPR", "carbon border adjustment") |
from_date | string | — | Restrict results to legislation published on or after this date in YYYY-MM-DD format (e.g. "2020-01-01"). Omit for all dates. |
Parameters from the server's own tool schema.
Why eurlex.legislation.search is rated Low
Tool queries and retrieves public EU legislation data with no side effects or data modification.
From the tool's definition Search official EUR-Lex Cellar SPARQL endpoint for EU legislative acts by keyword
Attacks that exploit this kind of access
The rule that runs eurlex.legislation.search 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.search, this is the rule to start with:
eurlex.legislation.search 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.search call is checked against it from then on.
Questions about eurlex.legislation.search
Search the official EUR-Lex Cellar SPARQL endpoint for EU legislative acts by keyword in English titles. Returns matching regulations, directives, and decisions with CELEX identifier, date, English title, in-force status, Cellar URI, and a direct EUR-Lex URL. Examples: keyword="artificial intelligence" returns the EU AI Act (32024R1689); keyword="GDPR" returns the General Data Protection Regulation (32016R0679). Results are ordered by most recent date first. Optionally restrict to acts published on or after from_date. CELEX format: 3 + 4-digit year + type letter (R=Regulation, L=Directive, D=Decision) + number. 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.search accepts 3 parameters: limit, keyword, from_date. Required: keyword. 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.search: 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.search 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.search 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.search. 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.search 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