Get a person attachment by ID
AI agents call getPersonAttachment to retrieve information from Follow Up Boss MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing data (a person's attachment) without creating, modifying, deleting, or executing any operations. It is a simple data query operation with minimal blast radius if misused by an AI agent—at worst, an agent could retrieve attachments it shouldn't have access to, but no data would be modified, deleted, or destroyed.
From the tool's definition Tool name 'getPersonAttachment' and description 'Get a person attachment by ID' indicate a retrieval operation. The verb 'Get' and action of fetching an attachment by identifier are characteristic of read-only operations with no modification or side effects.
Attacks that exploit this kind of access
Get a person attachment by ID. It is categorised as a Read tool in the Follow Up Boss MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Follow Up Boss MCP Server MCP server in PolicyLayer and add a rule for getPersonAttachment: 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.
getPersonAttachment is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the getPersonAttachment 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 getPersonAttachment. 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.
getPersonAttachment 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 →