Return the per-platform media and caption requirements (allowed formats, max file size, dimensions/aspect ratio, video duration, attachment counts, caption length, hashtag limits) enforced when scheduling a post. Call this BEFORE attaching media or writing a caption so the post passes validation ...
AI agents call get_media_requirements to retrieve information from Viraly MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves reference data about platform constraints. It has no side effects, does not modify any state, and poses minimal risk if misused by an AI agent—the worst outcome would be receiving accurate technical specifications. It clearly falls under the Read category (retrieves or queries data; no side effects).
From the tool's definition The tool description states it "Return[s] the per-platform media and caption requirements" and explicitly instructs to "Call this BEFORE attaching media or writing a caption." It retrieves and queries validation rules without modifying, creating, deleting, or…
Attacks that exploit this kind of access
Return the per-platform media and caption requirements (allowed formats, max file size, dimensions/aspect ratio, video duration, attachment counts, caption length, hashtag limits) enforced when scheduling a post. Call this BEFORE attaching media or writing a caption so the post passes validation on the first try. The API validates the same rules server-side and returns a friendly error listing exactly what to fix; note that video duration/dimension limits are best-effort because Viraly does not always measure server-side, so the target platform may still reject a non-conforming video. It is categorised as a Read tool in the Viraly MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Viraly MCP Server MCP server in PolicyLayer and add a rule for get_media_requirements: 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 Viraly MCP Server. Nothing to install.
get_media_requirements 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_media_requirements 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_media_requirements. 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_media_requirements is provided by the Viraly MCP Server MCP server (viraly-io/viraly-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 →