Map OCR data from ifr_ingest_document into an IFRS standard's input schema and validate it. Returns proposedInput, unmappedFields, missingRequiredFields, validation errors/warnings, needsUserInput[], and a confidence score. CRITICAL: proposedInput is a suggestion — every entry in needsUserInput[]...
Risk signalsBulk/mass operation — affects multiple targets
Part of the IfrCoworker server.
Free to start. No card required.
AI agents invoke ifr_propose_mapping to trigger processes or run actions in IfrCoworker. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
ifr_propose_mapping can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"ifr_propose_mapping": {
"limits": [
{
"counter": "ifr_propose_mapping_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full IfrCoworker policy for all 19 tools.
These attack patterns abuse exactly the kind of access ifr_propose_mapping gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Map OCR data from ifr_ingest_document into an IFRS standard's input schema and validate it. Returns proposedInput, unmappedFields, missingRequiredFields, validation errors/warnings, needsUserInput[], and a confidence score. CRITICAL: proposedInput is a suggestion — every entry in needsUserInput[] must be confirmed by the user before calling ifr_calculate. Never auto-calculate from unverified OCR data. FREE — no usage charge.. It is categorised as a Execute tool in the IfrCoworker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the IfrCoworker MCP server in PolicyLayer and add a rule for ifr_propose_mapping: 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_propose_mapping is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ifr_propose_mapping 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_propose_mapping. 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_propose_mapping 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.