Számla küldése e-mailben a partnernek vagy megadott címekre
AI agents invoke send_document to trigger actions in Billingo 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 triggers an external operation (sending an email) to a partner or specified addresses. It cannot be easily undone once the email is dispatched, and misuse could send incorrect invoices or spam to recipients. It falls under Execute as it triggers an external communication action rather than simply writing data internally.
From the tool's definition Számla küldése e-mailben a partnernek vagy megadott címekre — 'sending invoice by email to partner or specified addresses'
Documented attack patterns abuse exactly the kind of access send_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Billingo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for send_document:
{
"version": "1",
"default": "deny",
"tools": {
"send_document": {
"limits": [
{
"counter": "send_document_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}send_document 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.
Számla küldése e-mailben a partnernek vagy megadott címekre. It is categorised as a Execute tool in the Billingo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Billingo MCP Server MCP server in PolicyLayer and add a rule for send_document: 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 Billingo MCP Server. Nothing to install.
send_document 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 send_document 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 send_document. 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.
send_document is provided by the Billingo MCP Server MCP server (szotasz/billingo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Billingo 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.
42 Billingo MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.