Deep health scan: DNA completeness, campaigns, content, CRM, SEO, alerts. Returns traffic-light status per area.
AI agents call maasy_scan_brand to retrieve information from Maasy — AI Marketing Copilot without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool is purely informational and diagnostic in nature. It queries and reports on the state of marketing assets and metrics without modifying, deleting, executing commands, or moving resources. The worst-case misuse would be an agent gathering intelligence about brand health, which is a low-severity read operation.
From the tool's definition Tool performs a 'scan' and 'returns' status information with no action words like create, delete, update, execute, or modify.
Attacks that exploit this kind of access
Deep health scan: DNA completeness, campaigns, content, CRM, SEO, alerts. Returns traffic-light status per area. It is categorised as a Read tool in the Maasy — AI Marketing Copilot MCP Server, which means it retrieves data without modifying state.
Register the Maasy — AI Marketing Copilot MCP server in PolicyLayer and add a rule for maasy_scan_brand: 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_scan_brand 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 maasy_scan_brand 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_scan_brand. 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_scan_brand 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 →