retrieveRefreshTokenByIdWithId
Retrieves a single refresh token by unique Id. This is not the same thing as the string value of the refresh token. If you have that, you already have what you need.
This record as markdown: /tools/io-fusionauth-mcp-api/retrieverefreshtokenbyidwithid.md
What retrieveRefreshTokenByIdWithId does on Fusionauth
AI agents call retrieveRefreshTokenByIdWithId to retrieve information from Fusionauth without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why retrieveRefreshTokenByIdWithId is rated Low
This tool retrieves sensitive authentication tokens (refresh tokens) from the system. While categorized as Read (no side effects, only retrieval), the severity is high because refresh tokens are cryptographic credentials that could enable session hijacking or unauthorized API access if exposed to an attacker. The high blast radius justifies the elevated severity despite the benign Read category.
From the tool's definition Tool name contains 'retrieve' and description explicitly states 'Retrieves a single refresh token by unique Id', indicating a data query operation with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs retrieveRefreshTokenByIdWithId safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fusionauth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For retrieveRefreshTokenByIdWithId, this is the rule to start with:
retrieveRefreshTokenByIdWithId is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Fusionauth, apply this rule, and every retrieveRefreshTokenByIdWithId call is checked against it from then on.
Questions about retrieveRefreshTokenByIdWithId
Retrieves a single refresh token by unique Id. This is not the same thing as the string value of the refresh token. If you have that, you already have what you need. It is categorised as a Read tool in the Fusionauth MCP Server, which means it retrieves data without modifying state.
Register the Fusionauth MCP server in PolicyLayer and add a rule for retrieveRefreshTokenByIdWithId: 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 Fusionauth. Nothing to install.
retrieveRefreshTokenByIdWithId 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 retrieveRefreshTokenByIdWithId 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 retrieveRefreshTokenByIdWithId. 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.
retrieveRefreshTokenByIdWithId is provided by the Fusionauth MCP server (@fusionauth/mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fusionauth, and thousands of servers like it.
This server
Across the catalogue