Toggle fast mode for quicker, cheaper analysis.
AI agents use set_fast_mode to create or update resources in Screenshot Analyzer MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Screenshot Analyzer MCP environment.
This is a configuration write operation that reversibly changes system behavior (fast mode toggle). It modifies internal state but has no destructive, financial, or execute-level consequences. The change is easily reverted by toggling again.
From the tool's definition Tool name 'set_fast_mode' indicates it modifies a configuration setting. The sibling tool 'set_api_key' and 'set_reasoning_effort' (implied by context) confirm this server has stateful configuration tools.
Attacks that exploit this kind of access
Toggle fast mode for quicker, cheaper analysis. It is categorised as a Write tool in the Screenshot Analyzer MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Screenshot Analyzer MCP server in PolicyLayer and add a rule for set_fast_mode: 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 Screenshot Analyzer MCP. Nothing to install.
set_fast_mode 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 set_fast_mode 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 set_fast_mode. 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.
set_fast_mode is provided by the Screenshot Analyzer MCP server (sasuke-inu/ui-screenshot-android-review-openai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →