ukleg.legislation.sections
Get the complete list of sections, parts, and schedules (table of contents) for a specific piece of UK legislation. Returns each section with its type (section, schedule, part), number, title, and URL to the full section text. Use this to navigate the structure of an Act before retrieving specifi...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/ukleg.legislation.sections.md
What ukleg.legislation.sections does on Apibase
AI agents call ukleg.legislation.sections 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 |
|---|---|---|---|
type | string | Yes | Legislation type code. Common values: ukpga (UK Public General Acts), uksi (UK Statutory Instruments), asp (Scottish Parliament Acts), asc (Senedd Cymru/Wales A |
year | integer | Yes | Year the legislation was enacted (e.g. 2023 for legislation passed in 2023). |
number | integer | Yes | Chapter or instrument number within the year (e.g. 55 for the Online Safety Act 2023 c.55). |
Parameters from the server's own tool schema.
Why ukleg.legislation.sections is rated Low
Retrieves UK legislation structure and metadata without modifying data or executing code.
From the tool's definition Get complete list of sections, parts, schedules, table of contents, returns each section with type, number, title, URL.
Attacks that exploit this kind of access
The rule that runs ukleg.legislation.sections 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 ukleg.legislation.sections, this is the rule to start with:
ukleg.legislation.sections 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 ukleg.legislation.sections call is checked against it from then on.
Questions about ukleg.legislation.sections
Get the complete list of sections, parts, and schedules (table of contents) for a specific piece of UK legislation. Returns each section with its type (section, schedule, part), number, title, and URL to the full section text. Use this to navigate the structure of an Act before retrieving specific provisions. Requires the legislation type, year, and chapter number (use ukleg.legislation.search to find these). Example: type=ukpga, year=2023, number=55 returns all sections of the Online Safety Act 2023. Example: type=ukpga, year=1998, number=42 returns sections of the Human Rights Act 1998. Data source: legislation.gov.uk — The National Archives, Open Government Licence v3.0, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
ukleg.legislation.sections accepts 3 parameters: type, year, number. Required: type, year, number. 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 ukleg.legislation.sections: 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.
ukleg.legislation.sections 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 ukleg.legislation.sections 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 ukleg.legislation.sections. 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.
ukleg.legislation.sections 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