New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

fetch_alerts_grouped_per_customer

[Alert Manager 1.0] Fetches alerts of the specified customers. This API uses extended barrier mode by default.

SERVERAcronis Platform SOURCE@acronis-platform/mcp
Low RISK CLASS
Category Read
Parameters 10 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/acronis-platform-mcp/fetch-alerts-grouped-per-customer.md

What fetch_alerts_grouped_per_customer does on Acronis Platform

AI agents call fetch_alerts_grouped_per_customer to retrieve information from Acronis Platform without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
query object Query parameters

Parameters from the server's own tool schema.

Why fetch_alerts_grouped_per_customer is rated Low

Even though fetch_alerts_grouped_per_customer only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (18 properties)

Questions about fetch_alerts_grouped_per_customer

What does the fetch_alerts_grouped_per_customer tool do? +

[Alert Manager 1.0] Fetches alerts of the specified customers. This API uses extended barrier mode by default. It is categorised as a Read tool in the Acronis Platform MCP Server, which means it retrieves data without modifying state.

What parameters does fetch_alerts_grouped_per_customer accept? +

fetch_alerts_grouped_per_customer accepts 1 parameter: query. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fetch_alerts_grouped_per_customer? +

Register the Acronis Platform MCP server in PolicyLayer and add a rule for fetch_alerts_grouped_per_customer: 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 Acronis Platform. Nothing to install.

What risk level is fetch_alerts_grouped_per_customer? +

fetch_alerts_grouped_per_customer is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch_alerts_grouped_per_customer? +

Yes. Add a rate_limit block to the fetch_alerts_grouped_per_customer 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.

How do I block fetch_alerts_grouped_per_customer completely? +

Set action: deny in the PolicyLayer policy for fetch_alerts_grouped_per_customer. 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 fetch_alerts_grouped_per_customer? +

fetch_alerts_grouped_per_customer is provided by the Acronis Platform MCP server (@acronis-platform/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Acronis Platform, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Acronis Platform's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.