Update a pond
AI agents use updatePond 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.
The tool performs an update operation, which is characteristic of Write category tools that create or modify data reversibly. While 'pond' is not explicitly defined in the description, the context of a CRM system with CRUD operations and similar sibling tools (updatePeople, createCall, etc.) suggests this modifies some entity within the system.
From the tool's definition Tool name 'updatePond' indicates a modification operation. The description 'Update a pond' confirms this is a reversible data change operation. Context shows this is part of a CRM system with CRUD operations on various entities.
Attacks that exploit this kind of access
Update a pond. 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 updatePond: 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.
updatePond 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 updatePond 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 updatePond. 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.
updatePond 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 →