Get the authenticated user
AI agents call linkedin_get_profile to retrieve information from AmplifyrMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation on the authenticated user's profile. It has no capability to modify, delete, or execute actions. The read operation has minimal blast radius—an AI agent misusing this tool could only expose or log the user's own profile information, which the agent already has access to via authentication context. This is a standard Read category operation with low severity.
From the tool's definition Tool name and description: 'Get the authenticated user' - retrieves profile information for the currently authenticated user with no modifications or side effects.
Attacks that exploit this kind of access
Get the authenticated user. It is categorised as a Read tool in the AmplifyrMCP MCP Server, which means it retrieves data without modifying state.
Register the Amplifyr MCP server in PolicyLayer and add a rule for linkedin_get_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 AmplifyrMCP. Nothing to install.
linkedin_get_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 linkedin_get_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 linkedin_get_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.
linkedin_get_profile is provided by the Amplifyr MCP server (supersaiyane/amplifyrmcp). 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 →