meshes_retry_event_rule · Mesheshq MCP: Risk & Policy

WHAT IT DOES

What meshes_retry_event_rule does on Mesheshq

AI agents invoke meshes_retry_event_rule to trigger actions in Mesheshq. 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 meshes_retry_event_rule needs a policy

This tool re-executes a previously failed rule delivery, which is an external operation with side effects (triggering downstream integrations/actions). It is not purely a write (no new data created), not destructive, and not financial. It fits Execute because it triggers an external operation whose effects depend on the event and rule arguments.

From the tool's definition 'Manually retry a failed rule delivery for a specific event' — triggers an external operation (re-delivery of an event through a rule)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

meshes_retry_event_rule Rate-limited

meshes_retry_event_rule 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": {
    "meshes_retry_event_rule": {
      "limits": [
        {
          "counter": "meshes_retry_event_rule_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 Mesheshq, so you can run agents against it safely.

FAQ

Questions about meshes_retry_event_rule

What does the meshes_retry_event_rule tool do? +

Manually retry a failed rule delivery for a specific event. Use after investigating and fixing the underlying issue (e.g., expired credentials, misconfigured mapping). It is categorised as a Execute tool in the Mesheshq MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on meshes_retry_event_rule? +

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

What risk level is meshes_retry_event_rule? +

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

Can I rate-limit meshes_retry_event_rule? +

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

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

meshes_retry_event_rule is provided by the Mesheshq MCP server (mesheshq/meshes-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.