AI agents call get_user_info to retrieve information from Inoreader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user account information from an authenticated session. It performs a query operation with no ability to modify, delete, or execute arbitrary operations. The blast radius is minimal—exposing user metadata like email or account settings is a low-severity read operation. Confidence is high due to clear read-only semantics.
From the tool's definition Tool name 'get_user_info' and description 'Get current authenticated user information' indicates retrieval of user profile data with no side effects.
Attacks that exploit this kind of access
Get current authenticated user information. Costs 1 Zone 1 request. It is categorised as a Read tool in the Inoreader MCP Server, which means it retrieves data without modifying state.
Register the Inoreader MCP server in PolicyLayer and add a rule for get_user_info: 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 Inoreader. Nothing to install.
get_user_info 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_info 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_info. 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_info is provided by the Inoreader MCP server (justmytwospence/inoreader-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 →