One-call composite: T-number (T + 13 digits) → invoice registration status (NTA 適格請求書 API) + corporate details (NTA 法人番号 API). 日本語: T番号 1 つでインボイス登録状態と法人詳細を同時取得。Use when an AI agent receives a T-number (e.g. from invoice OCR) and needs to validate both invoice compliance and company identity in on...
Part of the Torify — Japan Locale APIs for AI Agents server.
Free to start. No card required.
AI agents call invoice.companyProfile to retrieve information from Torify — Japan Locale APIs for AI Agents without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though invoice.companyProfile only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"invoice.companyProfile": {}
}
}See the full Torify — Japan Locale APIs for AI Agents policy for all 24 tools.
These attack patterns abuse exactly the kind of access invoice.companyProfile gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
One-call composite: T-number (T + 13 digits) → invoice registration status (NTA 適格請求書 API) + corporate details (NTA 法人番号 API). 日本語: T番号 1 つでインボイス登録状態と法人詳細を同時取得。Use when an AI agent receives a T-number (e.g. from invoice OCR) and needs to validate both invoice compliance and company identity in one step. Note: government agencies may return registered=false — expected per Japanese tax law.. It is categorised as a Read tool in the Torify — Japan Locale APIs for AI Agents MCP Server, which means it retrieves data without modifying state.
Register the Torify — Japan Locale APIs for AI Agents MCP server in PolicyLayer and add a rule for invoice.companyProfile: 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 Torify — Japan Locale APIs for AI Agents. Nothing to install.
invoice.companyProfile 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 invoice.companyProfile 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 invoice.companyProfile. 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.
invoice.companyProfile is provided by the Torify — Japan Locale APIs for AI Agents MCP server (https://torify-mcp.torify.workers.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Torify — Japan Locale APIs for AI Agents tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.