AI agents call get_video_status to retrieve information from Creatify without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries the status of a video, which is a read-only operation with no side effects. Despite the empty description reducing confidence slightly, the semantic meaning of 'get_' prefix and 'status' suffix clearly indicates data retrieval rather than creation, modification, deletion, or execution.
From the tool's definition Tool name 'get_video_status' indicates retrieval of status information with no modification capability. The empty description limits certainty, but the naming convention strongly suggests a query operation.
Documented attack patterns abuse exactly the kind of access get_video_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Creatify, and nothing reaches the server without passing your rules. This is the rule we recommend for get_video_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_video_status": {}
}
}get_video_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_video_status. It is categorised as a Read tool in the Creatify MCP Server, which means it retrieves data without modifying state.
Register the Creatify MCP server in PolicyLayer and add a rule for 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 Creatify. Nothing to install.
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 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 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.
get_video_status is provided by the Creatify MCP server (tsavo/creatify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Creatify, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
13 Creatify tools catalogued and risk-classified — across an index of 43,000+ MCP servers.