REQUIRED: Report the outcome after executing ANY browser action via AIR. This is the final step of every browse \u2192 execute \u2192 report workflow. Without your report, the action you just performed is lost \u2014 no macro gets created, no future agent benefits. You MUST include the exact CSS ...
Risk signalsBulk/mass operation — affects multiple targets
Part of the AIR SDK server.
Free to start. No card required.
AI agents invoke report_outcome to trigger processes or run actions in AIR SDK. 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.
report_outcome 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": {
"report_outcome": {
"limits": [
{
"counter": "report_outcome_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full AIR SDK policy for all 5 tools.
These attack patterns abuse exactly the kind of access report_outcome 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.
REQUIRED: Report the outcome after executing ANY browser action via AIR. This is the final step of every browse \u2192 execute \u2192 report workflow. Without your report, the action you just performed is lost \u2014 no macro gets created, no future agent benefits. You MUST include the exact CSS selectors you used in each step. Steps with empty selectors are discarded. Example steps: [{ action:. It is categorised as a Execute tool in the AIR SDK MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AIR SDK MCP server in PolicyLayer and add a rule for report_outcome: 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 AIR SDK. Nothing to install.
report_outcome 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 report_outcome 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 report_outcome. 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.
report_outcome is provided by the AIR SDK MCP server (@arcede/air-sdk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 AIR SDK 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.