feature.add
Add an evidence-bound technical feature to the project graph.
This record as markdown: /tools/visionmcp/feature.add.md
What feature.add does on Visionmcp
AI agents use feature.add 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 feature.add is rated Medium
This tool creates or modifies project graph features, which is a reversible write operation. It does not execute arbitrary code, delete data, or move financial resources. The 'evidence-bound' qualifier suggests it operates within controlled constraints.
From the tool's definition Tool name 'add' and description 'Add an evidence-bound technical feature to the project graph' indicate creation/modification of project data structures.
Attacks that exploit this kind of access
The rule that runs feature.add 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 feature.add, this is the rule to start with:
feature.add 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 feature.add call is checked against it from then on.
Questions about feature.add
Add an evidence-bound technical feature to the project graph. 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 feature.add: 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.
feature.add 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 feature.add 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 feature.add. 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.
feature.add 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