One-call period-end close for agents with no IFRS knowledge. Pass an entityProfile (fact flags) plus the per-standard inputs as items[]; the engine runs the applicability checklist, executes the items as a dependency-ordered batch, and returns the full consolidated financial-statement package (tr...
Part of the IfrCoworker server.
Free to start. No card required.
AI agents use ifr_period_end_close to create or modify resources in IfrCoworker. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call ifr_period_end_close repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach IfrCoworker.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"ifr_period_end_close": {
"limits": [
{
"counter": "ifr_period_end_close_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full IfrCoworker policy for all 19 tools.
These attack patterns abuse exactly the kind of access ifr_period_end_close gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
One-call period-end close for agents with no IFRS knowledge. Pass an entityProfile (fact flags) plus the per-standard inputs as items[]; the engine runs the applicability checklist, executes the items as a dependency-ordered batch, and returns the full consolidated financial-statement package (trial balance, P&L, OCI, SOFP, XBRL-tagged journal entries) PLUS a coverage analysis flagging any standard the profile implies but no item was supplied for. Charged like ifr_period_end_batch (per successful item); the checklist/coverage portion is free.. It is categorised as a Write tool in the IfrCoworker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IfrCoworker MCP server in PolicyLayer and add a rule for ifr_period_end_close: 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_period_end_close is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ifr_period_end_close 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_period_end_close. 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_period_end_close 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.