crow_set_background
Set a previously generated gallery image as the current companion background
This record as markdown: /tools/kh0pper-crow/crow-set-background.md
What crow_set_background does on Crow
AI agents use crow_set_background to create or update resources in Crow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crow environment.
Why crow_set_background is rated Medium
This tool creates or modifies application state (the background setting) in a reversible manner. It selects and applies a pre-existing image from a gallery, which is a Write operation. No data is deleted, executed externally, or financially consequential. Severity is low because the blast radius of misuse is confined to cosmetic UI changes with no impact on data integrity, security, or functionality.
From the tool's definition Tool description states 'Set a previously generated gallery image as the current companion background' — this modifies the companion's visual configuration by updating the background setting.
Attacks that exploit this kind of access
The rule that runs crow_set_background safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For crow_set_background, this is the rule to start with:
crow_set_background 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 Crow, apply this rule, and every crow_set_background call is checked against it from then on.
Questions about crow_set_background
Set a previously generated gallery image as the current companion background. It is categorised as a Write tool in the Crow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Crow MCP server in PolicyLayer and add a rule for crow_set_background: 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 Crow. Nothing to install.
crow_set_background 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 crow_set_background 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 crow_set_background. 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.
crow_set_background is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
This server
Across the catalogue