eurlex.legislation.recent
Get the most recently published EU legislative acts from EUR-Lex Cellar. Returns acts ordered by publication date descending with CELEX identifier, date, English title (where available), in-force status, Cellar URI, and direct EUR-Lex URL. Covers all secondary EU legislation (regulations, directi...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/eurlex.legislation.recent.md
What eurlex.legislation.recent does on Apibase
AI agents call eurlex.legislation.recent 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 |
|---|---|---|---|
days | integer | — | Look back this many days for recently published EU legislation (1–365, default 30) |
limit | integer | — | Maximum number of results to return (1–20, default 10) |
Parameters from the server's own tool schema.
Why eurlex.legislation.recent is rated Low
Tool retrieves public legislative data from open-access repository with no side effects.
From the tool's definition Get the most recently published EU legislative acts, Returns acts ordered by publication date
Attacks that exploit this kind of access
The rule that runs eurlex.legislation.recent 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.recent, this is the rule to start with:
eurlex.legislation.recent 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.recent call is checked against it from then on.
Questions about eurlex.legislation.recent
Get the most recently published EU legislative acts from EUR-Lex Cellar. Returns acts ordered by publication date descending with CELEX identifier, date, English title (where available), in-force status, Cellar URI, and direct EUR-Lex URL. Covers all secondary EU legislation (regulations, directives, decisions) published within the specified number of days. Default look-back is 30 days; max 365 days. 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.recent accepts 2 parameters: days, limit. 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.recent: 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.recent 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.recent 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.recent. 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.recent 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