communications_planner
Plan communications cadence per stakeholder
This record as markdown: /tools/jrmatherly-mcp-context-forge/communications-planner.md
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 communications_planner is rated Medium
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
The rule that runs communications_planner safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ContextForge MCP Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For communications_planner, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect ContextForge MCP Gateway, apply this rule, and every communications_planner call is checked against it from then on.
Questions about communications_planner
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.
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.
communications_planner 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 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.
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.
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.
More on ContextForge MCP Gateway, and thousands of servers like it.
This server
Across the catalogue