communications_planner · ContextForge MCP Gateway MCP

WHAT IT DOES

What communications_planner does on ContextForge MCP Gateway

AI agents use communications_planner to create or update resources in ContextForge MCP Gateway — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ContextForge MCP Gateway environment.

WHY IT NEEDS A POLICY

Why communications_planner needs a policy

This tool performs a planning operation that creates communication plans or schedules—reversible data modifications. It does not retrieve data (Read), execute arbitrary code (Execute), delete irreversibly (Destructive), or move money (Financial). The 'plan' action is a Write-category operation that can be undone or modified.

From the tool's definition The tool name 'communications_planner' combined with the verb 'Plan' and description 'Plan communications cadence per stakeholder' indicates it creates or modifies communication schedules and plans.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

communications_planner Rate-limited

communications_planner 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "communications_planner": {
      "limits": [
        {
          "counter": "communications_planner_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about communications_planner

What does the communications_planner tool do? +

Plan communications cadence per stakeholder. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on communications_planner? +

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

What risk level is communications_planner? +

communications_planner is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit communications_planner? +

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

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

communications_planner is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.