AI agents call get_user_profile to retrieve information from Boma MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user profile information without creating, modifying, deleting, executing commands, or moving money. It is a straightforward read operation with minimal blast radius—the worst outcome is unauthorized access to profile data, which is lower severity than Write, Execute, or Destructive actions.
From the tool's definition Tool name 'get_user_profile' and description 'Get a user profile by ID' indicate data retrieval with no modification or side effects. The default scope to 'the authenticated user' further limits exposure.
Attacks that exploit this kind of access
Get a user profile by ID. Defaults to the authenticated user. It is categorised as a Read tool in the Boma MCP MCP Server, which means it retrieves data without modifying state.
Register the Boma MCP server in PolicyLayer and add a rule for get_user_profile: 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 Boma MCP. Nothing to install.
get_user_profile 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 get_user_profile 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 get_user_profile. 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.
get_user_profile is provided by the Boma MCP server (nicolasvegam/boma-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 →