AI agents use resolveBlocked to create or update resources in Ava — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ava environment.
The tool updates task status/state to mark a blocker as resolved—a reversible modification operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or involve financial operations. The blast radius is medium because incorrect use could mislead the team about task status in Slack, but changes are reversible via other state-modifying tools like pauseTask or updateTask.
From the tool's definition Tool name 'resolveBlocked' and description indicating reporting that blocking has been resolved. In context of task tracking (sibling tools: pauseTask, reportBlocked, startTask, etc.), this modifies task state to reflect resolution of a blocker.
Documented attack patterns abuse exactly the kind of access resolveBlocked gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ava, and nothing reaches the server without passing your rules. This is the rule we recommend for resolveBlocked:
{
"version": "1",
"default": "deny",
"tools": {
"resolveBlocked": {
"limits": [
{
"counter": "resolveblocked_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}resolveBlocked stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
ブロッキングが解決したことを報告する入力仕様。. It is categorised as a Write tool in the Ava MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ava MCP server in PolicyLayer and add a rule for resolveBlocked: 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 Ava. Nothing to install.
resolveBlocked 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 resolveBlocked 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 resolveBlocked. 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.
resolveBlocked is provided by the Ava MCP server (yutakobayashidev/ava). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ava, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
10 Ava tools catalogued and risk-classified — across an index of 43,000+ MCP servers.