category.select
Select the strongest category pack for the canonical target.
This record as markdown: /tools/visionmcp/category.select.md
What category.select does on Visionmcp
AI agents use category.select 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 category.select is rated Medium
This tool appears to select/set a category pack for a target, implying it modifies or assigns a configuration or metadata state. 'Select' in this context is more of a Write operation (choosing/setting a value) rather than a pure Read. The description is sparse, lowering confidence, but the action of selecting and applying something to a canonical target suggests a state change.
From the tool's definition "Select the strongest category pack for the canonical target"
Attacks that exploit this kind of access
The rule that runs category.select 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 category.select, this is the rule to start with:
category.select 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 category.select call is checked against it from then on.
Questions about category.select
Select the strongest category pack for the canonical target. 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 category.select: 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.
category.select 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 category.select 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 category.select. 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.
category.select 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