AI agents call openart_get_video_status to retrieve information from Openart without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about an existing video resource. It queries data without creating, modifying, deleting, or executing any operations. The blast radius is minimal—an agent misusing this tool could only retrieve status information it may not be authorized to see, not cause any destructive or financial impact.
From the tool's definition Tool description states 'Check the rendering status and URL' which is purely a query/retrieval operation with no modification or side effects. The verb 'check' and 'get' are characteristic of Read operations.
Attacks that exploit this kind of access
Check the rendering status and URL of an OpenArt video by ID. It is categorised as a Read tool in the Openart MCP Server, which means it retrieves data without modifying state.
Register the Openart MCP server in PolicyLayer and add a rule for openart_get_video_status: 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 Openart. Nothing to install.
openart_get_video_status 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 openart_get_video_status 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 openart_get_video_status. 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.
openart_get_video_status is provided by the Openart MCP server (jbertus/openart-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 →