Compose and publish a post on a social platform (linkedin, x, medium). Uses the platform adapter pattern — handles shadow DOM, selectors, and compose flows automatically. The browser must be logged into the platform.
AI agents use scout_post to create or update resources in Scout — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scout environment.
This tool creates new content on social platforms, making it a Write action. Severity is medium because misuse could result in unauthorized or harmful posts published to the user's accounts, but the damage is reversible (posts can be deleted).
From the tool's definition Tool description states 'Compose and publish a post on a social platform (linkedin, x, medium)' — explicit mention of publishing content, which is a write operation that modifies platform state.
Attacks that exploit this kind of access
Compose and publish a post on a social platform (linkedin, x, medium). Uses the platform adapter pattern — handles shadow DOM, selectors, and compose flows automatically. The browser must be logged into the platform. It is categorised as a Write tool in the Scout MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scout MCP server in PolicyLayer and add a rule for scout_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 Scout. Nothing to install.
scout_post is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scout_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 scout_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.
scout_post is provided by the Scout MCP server (lautrek/scout). 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 →