AI agents call get_video_job to retrieve information from Posterly 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 video generation jobs. It performs read-only queries to fetch job data or list recent jobs. There are no side effects, data modifications, code execution, or irreversible actions. The highest severity artifact would be information disclosure of job metadata, which is minimal in context of a social media scheduling service.
From the tool's definition Tool description states 'Get one Veo video generation job by ID, or list recent video jobs' — operations are purely retrieval (get, list) with no modification or execution of side effects.
Attacks that exploit this kind of access
Get one Veo video generation job by ID, or list recent video jobs when job_id is omitted. Use after generate_video to poll for completed video_url. It is categorised as a Read tool in the Posterly MCP Server, which means it retrieves data without modifying state.
Register the Posterly MCP server in PolicyLayer and add a rule for get_video_job: 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 Posterly. Nothing to install.
get_video_job 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_job 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_job. 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_job is provided by the Posterly MCP server (posterly-mcp-server). 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 →