Save cluster-level alert settings (like repeat tolerance)
AI agents use ambari_alerts_savealertsettings to create or update resources in Ambari MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ambari MCP Server environment.
This tool creates or modifies alert settings at the cluster level. While it affects alerts—which are critical for operational awareness—the changes are reversible and represent data modification rather than destruction.
From the tool's definition Tool name contains 'save' and description states 'Save cluster-level alert settings'; modifies configuration (repeat tolerance) without deletion or irreversible effects.
Attacks that exploit this kind of access
Save cluster-level alert settings (like repeat tolerance). It is categorised as a Write tool in the Ambari MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ambari MCP Server MCP server in PolicyLayer and add a rule for ambari_alerts_savealertsettings: 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 Ambari MCP Server. Nothing to install.
ambari_alerts_savealertsettings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ambari_alerts_savealertsettings 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 ambari_alerts_savealertsettings. 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.
ambari_alerts_savealertsettings is provided by the Ambari MCP Server MCP server (nikita15p/ambari-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 →