role.list
List persistent role-task handoffs in priority order.
This record as markdown: /tools/visionmcp/role.list.md
What role.list does on Visionmcp
AI agents call role.list to retrieve information from Visionmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why role.list is rated Low
This tool retrieves and presents role-task handoff information in priority order. It has no side effects, does not modify state, and does not trigger external operations. It is a straightforward data retrieval operation typical of Read category tools.
From the tool's definition Tool name contains 'list' and description states it 'List[s] persistent role-task handoffs' — a query operation that retrieves existing data without modification.
Attacks that exploit this kind of access
The rule that runs role.list 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.list, this is the rule to start with:
role.list is read-only, so it stays allowed. 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.list call is checked against it from then on.
Questions about role.list
List persistent role-task handoffs in priority order. It is categorised as a Read tool in the Visionmcp MCP Server, which means it retrieves data without modifying state.
Register the Vision MCP server in PolicyLayer and add a rule for role.list: 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.list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the role.list 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.list. 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.list 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