Get the authenticated Medium user profile.
AI agents call medium_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 retrieves profile information for an authenticated Medium user. It performs a query operation with no side effects—it does not create, modify, delete, or execute any external actions. The blast radius of misuse is minimal, as reading profile data poses low risk. Confidence is high due to the clear read-only semantics of 'get' and the absence of any mutation language in the description.
From the tool's definition Tool name 'medium_get_profile' and description 'Get the authenticated Medium user profile' indicate a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Get the authenticated Medium user profile. 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 medium_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.
medium_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 medium_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 medium_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.
medium_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 →