Medium Risk

email_reports_core_create

Create a scheduled "core" email report covering analytics, events, crashes, and star-rating for one or more apps via /i/reports/create?report_type=core. Requires the reports plugin. For dashboard-based reports use email_reports_dashboard_create.

Part of the Countly MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use email_reports_core_create to create or modify resources in Countly. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call email_reports_core_create repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Countly.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

countly.yaml
tools:
  email_reports_core_create:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Countly policy for all 127 tools.

Tool Name email_reports_core_create
Category Write
MCP Server Countly MCP Server
Risk Level Medium

View all 127 tools →

Agents calling write-class tools like email_reports_core_create have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the email_reports_core_create tool do? +

Create a scheduled "core" email report covering analytics, events, crashes, and star-rating for one or more apps via /i/reports/create?report_type=core. Requires the reports plugin. For dashboard-based reports use email_reports_dashboard_create.. It is categorised as a Write tool in the Countly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on email_reports_core_create? +

Add a rule in your Intercept YAML policy under the tools section for email_reports_core_create. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Countly MCP server.

What risk level is email_reports_core_create? +

email_reports_core_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit email_reports_core_create? +

Yes. Add a rate_limit block to the email_reports_core_create rule in your Intercept 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.

How do I block email_reports_core_create completely? +

Set action: deny in the Intercept policy for email_reports_core_create. 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.

What MCP server provides email_reports_core_create? +

email_reports_core_create is provided by the Countly MCP server (countly-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.