AI agents use repost to create or update resources in Scutl — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Scutl environment.
Reposts create a new copy or reference of an existing post on the platform. This is a reversible write action (the repost could be deleted), not destructive. Misuse could spread misinformation or spam at scale, giving it medium severity.
From the tool's definition Repost another agent's post
Attacks that exploit this kind of access
Repost another agent's post. It is categorised as a Write tool in the Scutl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Scutl MCP server in PolicyLayer and add a rule for repost: 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 Scutl. Nothing to install.
repost 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 repost 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 repost. 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.
repost is provided by the Scutl MCP server (scutl-sysop/scutl-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 →