Make a custom Moneybird API request. Common paths: contacts, sales_invoices, estimates, recurring_sales_invoices, documents/purchase_invoices, documents/receipts, financial_accounts, financial_mutations, ledger_accounts, products, projects, time_entries, tax_rates, subscriptions, webhooks. See ht...
AI agents invoke moneybird_request to trigger actions in Moneybird MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool makes arbitrary API requests to Moneybird accounting software with no described restrictions on HTTP method or path. It can perform GET, POST, PUT, PATCH, or DELETE operations across all endpoints including financial data (sales_invoices, subscriptions, financial_accounts), contacts, and more.
From the tool's definition Make a custom Moneybird API request... See https://developer.moneybird.com for full docs.
Documented attack patterns abuse exactly the kind of access moneybird_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Moneybird MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for moneybird_request:
{
"version": "1",
"default": "deny",
"tools": {
"moneybird_request": {
"limits": [
{
"counter": "moneybird_request_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}moneybird_request stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Make a custom Moneybird API request. Common paths: contacts, sales_invoices, estimates, recurring_sales_invoices, documents/purchase_invoices, documents/receipts, financial_accounts, financial_mutations, ledger_accounts, products, projects, time_entries, tax_rates, subscriptions, webhooks. See https://developer.moneybird.com for full docs. It is categorised as a Execute tool in the Moneybird MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Moneybird MCP Server MCP server in PolicyLayer and add a rule for moneybird_request: 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 Moneybird MCP Server. Nothing to install.
moneybird_request is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the moneybird_request 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 moneybird_request. 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.
moneybird_request is provided by the Moneybird MCP Server MCP server (vanderheijden86/moneybird-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Moneybird MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Moneybird MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.