Generate on-brand social content using maasy AI. Respects brand DNA, tone, ICP.
AI agents use maasy_generate_content to create or update resources in Maasy — AI Marketing Copilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Maasy — AI Marketing Copilot environment.
This tool generates and creates marketing content (social media posts) reversibly; content can be edited or deleted afterward. It modifies the marketing asset state by adding new content items. This is a Write operation, not Read (it creates, not just retrieves), not Execute (no arbitrary code/external ops), not Destructive (reversible).
From the tool's definition 'Generate on-brand social content' — the tool creates new content artifacts (social posts) that are persisted and publishable.
Attacks that exploit this kind of access
Generate on-brand social content using maasy AI. Respects brand DNA, tone, ICP. It is categorised as a Write tool in the Maasy — AI Marketing Copilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Maasy — AI Marketing Copilot MCP server in PolicyLayer and add a rule for maasy_generate_content: 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 Maasy — AI Marketing Copilot. Nothing to install.
maasy_generate_content 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 maasy_generate_content 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 maasy_generate_content. 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.
maasy_generate_content is provided by the Maasy — AI Marketing Copilot MCP server (@maasy-ai/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 →