AI agents call get_available_effects to retrieve information from Ulanzi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a static list of supported visual effects from the Ulanzi TC001 clock device. It performs a read-only query with no capability to modify state, execute commands, delete data, or commit financial actions. The blast radius of misuse is minimal—an agent cannot cause harm by repeatedly querying this list.
From the tool's definition Tool name 'get_available_effects' and description 'Get list of all available visual effects' indicate a query/retrieval operation with no data modification or side effects.
Attacks that exploit this kind of access
Get list of all available visual effects. It is categorised as a Read tool in the Ulanzi MCP Server, which means it retrieves data without modifying state.
Register the Ulanzi MCP server in PolicyLayer and add a rule for get_available_effects: 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 Ulanzi. Nothing to install.
get_available_effects is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_available_effects 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 get_available_effects. 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.
get_available_effects is provided by the Ulanzi MCP server (jelloeater/ulanzi-mcp). 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 →