Retrieve recent SMS marketing campaigns and their deployment status. Useful for an AI agent to check what has already been sent before drafting a new one.
AI agents call list_campaigns to retrieve information from Postscript without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves campaign metadata and deployment status without creating, modifying, deleting, or executing any actions. It poses minimal risk; an agent misusing it could only over-query or enumerate campaigns, not cause direct harm.
From the tool's definition Tool description states 'Retrieve recent SMS marketing campaigns' — a read-only operation. No modification, deletion, execution, or financial activity is described.
Attacks that exploit this kind of access
Retrieve recent SMS marketing campaigns and their deployment status. Useful for an AI agent to check what has already been sent before drafting a new one. It is categorised as a Read tool in the Postscript MCP Server, which means it retrieves data without modifying state.
Register the Postscript MCP server in PolicyLayer and add a rule for list_campaigns: 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 Postscript. Nothing to install.
list_campaigns 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 list_campaigns 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 list_campaigns. 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.
list_campaigns is provided by the Postscript MCP server (nobanks/postscript-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 →