Low Risk

get_document

Számla/bizonylat részleteinek lekérése ID alapján

How to control get_document ↓

What get_document does on Billingo MCP Server

AI agents call get_document to retrieve information from Billingo MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_document needs a policy

This tool queries and returns document/invoice details based on an identifier. It performs a read-only retrieval operation with no capability to modify, delete, or execute operations. The impact of misuse is limited to information disclosure, making it a low-severity Read category tool.

From the tool's definition Tool name 'get_document' and description 'Számla/bizonylat részleteinek lekérése ID alapján' (Hungarian: 'Retrieving invoice/document details by ID') indicate a retrieval operation with no side effects.

Documented attack patterns abuse exactly the kind of access get_document gives an agent:

How to control get_document

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 get_document:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_document": {}
  }
}

get_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Billingo MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_document

What does the get_document tool do? +

Számla/bizonylat részleteinek lekérése ID alapján. It is categorised as a Read tool in the Billingo MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_document? +

Register the Billingo MCP Server MCP server in PolicyLayer and add a rule for get_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.

What risk level is get_document? +

get_document is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_document? +

Yes. Add a rate_limit block to the get_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.

How do I block get_document completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_document? +

get_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.

Enforce policy on every Billingo MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.