test_contact_point · Grafana MCP Server MCP: Risk & Policy

WHAT IT DOES

What test_contact_point does on Grafana MCP Server

AI agents invoke test_contact_point to trigger actions in Grafana MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why test_contact_point needs a policy

This tool triggers an external operation — sending a notification — to a contact point. It doesn't merely read or write data; it actively dispatches a message to an external system. While it's labeled 'test', it still causes a real side effect (a notification is sent). This fits Execute since it triggers an external operation whose effects depend on arguments.

From the tool's definition Send a test notification to a contact point

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_contact_point Rate-limited

test_contact_point stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_contact_point": {
      "limits": [
        {
          "counter": "test_contact_point_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Grafana MCP Server, so you can run agents against it safely.

FAQ

Questions about test_contact_point

What does the test_contact_point tool do? +

Send a test notification to a contact point. It is categorised as a Execute tool in the Grafana MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_contact_point? +

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

What risk level is test_contact_point? +

test_contact_point is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit test_contact_point? +

Yes. Add a rate_limit block to the test_contact_point 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 test_contact_point completely? +

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

test_contact_point is provided by the Grafana MCP Server MCP server (quanticsoul4772/grafana-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.