Get user account information including name, email, subscription status, and registration date.
AI agents call user_profile to retrieve information from Raindrop Io MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure read operation that queries and retrieves existing user profile data without modifying, deleting, executing code, or committing financial transactions. The blast radius if misused by an agent is minimal — it gains visibility into non-sensitive metadata already associated with the authenticated user account.
From the tool's definition Tool description states 'Get user account information' — a retrieval operation with no side effects. Returns read-only data: name, email, subscription status, and registration date.
Attacks that exploit this kind of access
Get user account information including name, email, subscription status, and registration date. It is categorised as a Read tool in the Raindrop Io MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Raindrop Io MCP Server MCP server in PolicyLayer and add a rule for 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 Raindrop Io MCP Server. Nothing to install.
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 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 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.
user_profile is provided by the Raindrop Io MCP Server MCP server (kazuph/mcp-raindrop). 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 →