review.model_tier
Record a tier decision; acceptance cannot exceed a valid receipt's fidelity.
This record as markdown: /tools/visionmcp/review.model-tier.md
What review.model_tier does on Visionmcp
AI agents use review.model_tier 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 review.model_tier is rated Medium
The tool records (writes) a tier decision, which is a durable state change in the system. It does not delete data or execute arbitrary code. The constraint 'acceptance cannot exceed a valid receipt's fidelity' implies validation logic around the write, not a destructive or financial operation.
From the tool's definition 'Record a tier decision' — the tool writes/commits a tier classification decision for a model
Attacks that exploit this kind of access
The rule that runs review.model_tier 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 review.model_tier, this is the rule to start with:
review.model_tier 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 review.model_tier call is checked against it from then on.
Questions about review.model_tier
Record a tier decision; acceptance cannot exceed a valid receipt's fidelity. 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 review.model_tier: 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.
review.model_tier 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 review.model_tier 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 review.model_tier. 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.
review.model_tier 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