Today
AI agents call maasy_get_daily_summary 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.
This tool retrieves or queries summary information for the current day—a read-only operation with no side effects. It fits the Read category as it provides data consumption without state changes. Low severity due to read-only nature and typical scope of daily summaries in marketing contexts.
From the tool's definition Tool name 'maasy_get_daily_summary' and description 'Today' indicate retrieval of summary data. The tool is part of a marketing copilot suite where sibling tools like 'maasy_get_alerts' and 'maasy_get_campaign_metrics' also retrieve data without modification.
Attacks that exploit this kind of access
Today. 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_get_daily_summary: 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_get_daily_summary 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_get_daily_summary 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_get_daily_summary. 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_get_daily_summary 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 →