Install an inbox app for a user. Requires the publishedInboxAppId from FUB
AI agents use inboxAppInstall 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.
This tool creates a new configuration or resource (app installation) within the Follow Up Boss CRM system. It modifies user state reversibly—an installed app can be uninstalled. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name 'inboxAppInstall' and description 'Install an inbox app for a user' indicates a create/modify operation that adds a new app installation to a user's inbox configuration.
Attacks that exploit this kind of access
Install an inbox app for a user. Requires the publishedInboxAppId from FUB. 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.
Register the Follow Up Boss MCP Server MCP server in PolicyLayer and add a rule for inboxAppInstall: 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.
inboxAppInstall 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 inboxAppInstall 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 inboxAppInstall. 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.
inboxAppInstall 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →