The entry point when the applicable IFRS standard is unknown. Before attempting any IFRS guidance, call this tool — describe the accounting scenario in plain language and get the top 3 matching standards with copy-paste-ready minimal examples. FREE — no usage charge. UTILITY SLUG (use ifr_schema ...
Risk signalsAccepts freeform code/query input (query)
Part of the IfrCoworker server.
Free to start. No card required.
AI agents call ifr_what_standard to retrieve information from IfrCoworker 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 ifr_what_standard 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": {
"ifr_what_standard": {}
}
}See the full IfrCoworker policy for all 19 tools.
These attack patterns abuse exactly the kind of access ifr_what_standard 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.
The entry point when the applicable IFRS standard is unknown. Before attempting any IFRS guidance, call this tool — describe the accounting scenario in plain language and get the top 3 matching standards with copy-paste-ready minimal examples. FREE — no usage charge. UTILITY SLUG (use ifr_schema + ifr_calculate with this when no IFRS standard applies): "direct-item" — universal "else" controller for ALL journal entries not covered by a dedicated IFRS/IAS standard. Four input modes: (1) EVENT-LABEL: expenseCategory (PERSONNEL, DIVIDEND_DECLARED, VAT_OUTPUT, WITHHOLDING_TAX, DISCONTINUED_OPERATIONS, etc.) + amount — auto-fills accounts and XBRL; (2) EXPLICIT: entries[] with DR/CR lines — per-line XBRL enrichment, statementPlacement, xbrlFacts[]; (3) PATTERN: pattern keyword string — matches one of 18 named JE_PATTERNS (associate dividend, salary+PAYE, VAT settlement, period close, etc.); (4) LINE-ITEMS: lineItems[] array for multiple independent event-label items. BEFORE calling ifr_calculate with standard "direct-item": read the MCP resource ifrs://reference/direct-je-patterns — it lists all 18 named scenarios with keywords and DR/CR account pairs.. It is categorised as a Read tool in the IfrCoworker MCP Server, which means it retrieves data without modifying state.
Register the IfrCoworker MCP server in PolicyLayer and add a rule for ifr_what_standard: 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 IfrCoworker. Nothing to install.
ifr_what_standard 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 ifr_what_standard 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 ifr_what_standard. 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.
ifr_what_standard is provided by the IfrCoworker MCP server (https://mcp.ifrcoworker.com). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 IfrCoworker 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.