bank-of-england.rates.bank_rate
Daily history of the Bank of England Official Bank Rate (the UK base interest rate set by the Monetary Policy Committee), series IUDBEDR. Returns the most recent N days (default 90, max 1825). Data: Bank of England Statistical Interactive Database (bankofengland.co.uk/boeapps/database), no auth r...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bank-of-england.rates.bank-rate.md
What bank-of-england.rates.bank_rate does on Apibase
AI agents use bank-of-england.rates.bank_rate to create or update resources in Apibase, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apibase environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
last_n | integer | — | Number of most recent calendar days to return, counting back from today (default 90, max 1825 = 5 years). This is a daily series. |
Parameters from the server's own tool schema.
Why bank-of-england.rates.bank_rate is rated Medium
An AI agent can call bank-of-england.rates.bank_rate faster than any human can review: one bad instruction and it creates or modifies resources in Apibase by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs bank-of-england.rates.bank_rate 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 bank-of-england.rates.bank_rate, this is the rule to start with:
bank-of-england.rates.bank_rate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 bank-of-england.rates.bank_rate call is checked against it from then on.
Questions about bank-of-england.rates.bank_rate
Daily history of the Bank of England Official Bank Rate (the UK base interest rate set by the Monetary Policy Committee), series IUDBEDR. Returns the most recent N days (default 90, max 1825). Data: Bank of England Statistical Interactive Database (bankofengland.co.uk/boeapps/database), no auth required, UK Open Government Licence v3.0. It is categorised as a Write tool in the Apibase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
bank-of-england.rates.bank_rate accepts 1 parameter: last_n. 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 bank-of-england.rates.bank_rate: 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.
bank-of-england.rates.bank_rate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the bank-of-england.rates.bank_rate 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 bank-of-england.rates.bank_rate. 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.
bank-of-england.rates.bank_rate 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