Search CupShup blog articles for marketing insights, strategies, and industry trends. Topics include BTL marketing, brand activation, experiential marketing, sampling campaigns, sensory marketing, community marketing, and more.
Part of the CupShup Marketing Knowledge Base server.
Free to start. No card required.
AI agents call get_blog_insights to retrieve information from CupShup Marketing Knowledge Base without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_blog_insights only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_blog_insights": {}
}
}See the full CupShup Marketing Knowledge Base policy for all 5 tools.
These attack patterns abuse exactly the kind of access get_blog_insights gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Search CupShup blog articles for marketing insights, strategies, and industry trends. Topics include BTL marketing, brand activation, experiential marketing, sampling campaigns, sensory marketing, community marketing, and more.. It is categorised as a Read tool in the CupShup Marketing Knowledge Base MCP Server, which means it retrieves data without modifying state.
Register the CupShup Marketing Knowledge Base MCP server in PolicyLayer and add a rule for get_blog_insights: 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 CupShup Marketing Knowledge Base. Nothing to install.
get_blog_insights 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 get_blog_insights 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 get_blog_insights. 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.
get_blog_insights is provided by the CupShup Marketing Knowledge Base MCP server (sidharth-5u15/cupshup-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 CupShup Marketing Knowledge Base tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.