Get full details for a single post — caption, attachments, channel, schedule, metrics. Use this when the user asks about a specific post or when another tool returned a post id worth inspecting.
AI agents call get_post 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 is a data retrieval operation that queries post information without creating, modifying, deleting, or executing any actions. It is a simple read-only query of existing post data.
From the tool's definition Tool name 'get_post' and description states it retrieves full details for a single post (caption, attachments, channel, schedule, metrics) with no mention of modifications or side effects.
Attacks that exploit this kind of access
Get full details for a single post — caption, attachments, channel, schedule, metrics. Use this when the user asks about a specific post or when another tool returned a post id worth inspecting. 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_post: 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_post 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_post 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_post. 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_post 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 →