Get details of a single campaign on PostEverywhere by its id, including post_count.
AI agents call get_campaign to retrieve information from Posteverywhere without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation—fetching campaign metadata by ID. It has no side effects, does not create, modify, or delete data, and does not execute external operations. The blast radius of misuse is minimal (information disclosure only). Despite the server's broader social media publishing capabilities, this specific tool is purely Read-category.
From the tool's definition Tool name is 'get_campaign' and description states 'Get details of a single campaign...including post_count', using retrieve language ('Get') with no modification or deletion capabilities.
Attacks that exploit this kind of access
Get details of a single campaign on PostEverywhere by its id, including post_count. It is categorised as a Read tool in the Posteverywhere MCP Server, which means it retrieves data without modifying state.
Register the Posteverywhere MCP server in PolicyLayer and add a rule for get_campaign: 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 Posteverywhere. Nothing to install.
get_campaign 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_campaign 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_campaign. 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_campaign is provided by the Posteverywhere MCP server (posteverywhere/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 →