role.waiting
Mark an advisory role task as waiting for explicit external input.
This record as markdown: /tools/visionmcp/role.waiting.md
What role.waiting does on Visionmcp
AI agents use role.waiting to create or update resources in Visionmcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Visionmcp environment.
Why role.waiting is rated Medium
The tool modifies the state of a task by marking it as 'waiting', which is a reversible state change (Write). It does not delete data, execute code, or have financial implications. The blast radius is low as it only affects task status within the system.
From the tool's definition Mark an advisory role task as waiting for explicit external input
Attacks that exploit this kind of access
The rule that runs role.waiting safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For role.waiting, this is the rule to start with:
role.waiting 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every role.waiting call is checked against it from then on.
Questions about role.waiting
Mark an advisory role task as waiting for explicit external input. It is categorised as a Write tool in the Visionmcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Vision MCP server in PolicyLayer and add a rule for role.waiting: 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 Visionmcp. Nothing to install.
role.waiting 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 role.waiting 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 role.waiting. 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.
role.waiting is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
This server
Across the catalogue