portfolio.record_result
Attach evidence outputs and scores to one isolated portfolio candidate.
This record as markdown: /tools/visionmcp/portfolio.record-result.md
What portfolio.record_result does on Visionmcp
AI agents use portfolio.record_result 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 portfolio.record_result is rated Medium
The tool creates or modifies data by attaching evidence outputs and scores to a portfolio candidate. This is a reversible write operation — it does not delete data, execute code, or involve financial transactions. Misuse could corrupt model evaluation records, hence medium severity.
From the tool's definition Attach evidence outputs and scores to one isolated portfolio candidate
Attacks that exploit this kind of access
The rule that runs portfolio.record_result 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 portfolio.record_result, this is the rule to start with:
portfolio.record_result 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 portfolio.record_result call is checked against it from then on.
Questions about portfolio.record_result
Attach evidence outputs and scores to one isolated portfolio candidate. 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 portfolio.record_result: 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.
portfolio.record_result 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 portfolio.record_result 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 portfolio.record_result. 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.
portfolio.record_result 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