Adószám ellenőrzése a NAV rendszerében. Visszaadja a cég nevét és címét ha érvényes.
AI agents call check_tax_number 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.
This tool performs a lookup operation against an external registry to validate and retrieve publicly available information about a company based on its tax number. It has no side effects, does not modify data, and does not execute arbitrary operations. It is a straightforward Read operation similar to a search or database query.
From the tool's definition Tool name 'check_tax_number' and description indicate it validates a tax number in the NAV (Hungarian tax authority) system and returns company name and address if valid.
Documented attack patterns abuse exactly the kind of access check_tax_number 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 check_tax_number:
{
"version": "1",
"default": "deny",
"tools": {
"check_tax_number": {}
}
}check_tax_number is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Adószám ellenőrzése a NAV rendszerében. Visszaadja a cég nevét és címét ha érvényes. It is categorised as a Read tool in the Billingo MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Billingo MCP Server MCP server in PolicyLayer and add a rule for check_tax_number: 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.
check_tax_number 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 check_tax_number 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 check_tax_number. 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.
check_tax_number 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.