AI agents call speedrun_get_user to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
user_id | string | Yes | User ID or username |
Parameters from the server's own tool schema.
This tool queries and returns publicly available user profile data from Speedrun.com without creating, modifying, deleting, or executing any operations. It is a straightforward read-only data retrieval function with minimal security risk.
From the tool's definition Tool name contains 'get_' and description states 'Get a Speedrun.com user profile' — this is a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get a Speedrun.com user profile by ID or username. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
speedrun_get_user accepts 1 parameter: user_id. Required: user_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for speedrun_get_user: 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 UnClick. Nothing to install.
speedrun_get_user 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 speedrun_get_user 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 speedrun_get_user. 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.
speedrun_get_user is provided by the UnClick MCP server (@unclick/mcp-server). 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 →