AI agents use add_communication_to_case to create or update resources in Prometheus MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prometheus MCP Server environment.
The tool performs a reversible create/modify operation (adding communication to a case) rather than deletion or financial action. While the empty description limits certainty, the naming convention strongly suggests it writes data to case management records. Classified as Write with medium severity due to potential case workflow disruption if misused, and medium confidence due to lacking a formal description.
From the tool's definition Tool name 'add_communication_to_case' indicates modification of case data by appending communication records. The 'add_' prefix suggests a write operation that creates or modifies data. Description is empty, reducing confidence.
Documented attack patterns abuse exactly the kind of access add_communication_to_case gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Prometheus MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for add_communication_to_case:
{
"version": "1",
"default": "deny",
"tools": {
"add_communication_to_case": {
"limits": [
{
"counter": "add_communication_to_case_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_communication_to_case stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
add_communication_to_case. It is categorised as a Write tool in the Prometheus MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prometheus MCP Server MCP server in PolicyLayer and add a rule for add_communication_to_case: 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 Prometheus MCP Server. Nothing to install.
add_communication_to_case 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 add_communication_to_case 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 add_communication_to_case. 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.
add_communication_to_case is provided by the Prometheus MCP Server MCP server (awslabs.prometheus-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Prometheus MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
805 Prometheus MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.