inboxAppCreateParticipant · Follow Up Boss MCP Server MCP

WHAT IT DOES

What inboxAppCreateParticipant does on Follow Up Boss MCP Server

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

WHY IT NEEDS A POLICY

Why inboxAppCreateParticipant needs a policy

The tool adds a participant to an existing conversation, which modifies the state of that conversation. This is a Write operation (reversible data modification) rather than Read (no side effects) or Destructive (irreversible deletion).

From the tool's definition Tool description states 'Add a participant to an inbox app conversation' — this creates/modifies a conversation by adding a participant, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

inboxAppCreateParticipant Rate-limited

inboxAppCreateParticipant 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": {
    "inboxAppCreateParticipant": {
      "limits": [
        {
          "counter": "inboxappcreateparticipant_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 Follow Up Boss MCP Server, so you can run agents against it safely.

FAQ

Questions about inboxAppCreateParticipant

What does the inboxAppCreateParticipant tool do? +

Add a participant to an inbox app conversation. It is categorised as a Write tool in the Follow Up Boss MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on inboxAppCreateParticipant? +

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

What risk level is inboxAppCreateParticipant? +

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

Can I rate-limit inboxAppCreateParticipant? +

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

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

inboxAppCreateParticipant is provided by the Follow Up Boss MCP Server MCP server (nerdsnipe-inc/follow-up-boss-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.