Mint a fresh short-lived access-token from the partner api-secret. Some Partner API tiers require this token (sent as the access-token header) on order/user endpoints. The token is short-lived (~minutes); cache it and refresh on 401. Returns { accessToken, expiresAt }.
AI agents call refresh_access_token as a supporting operation in Mcp Ap2 workflows.
This tool generates an authentication token from an existing secret credential. It does not read user data, write/modify records, execute commands, delete anything, or move money. It is purely an auth/credential-management operation — minting a short-lived JWT/token for subsequent API calls.
From the tool's definition Mint a fresh short-lived access-token from the partner api-secret... The token is short-lived (~minutes); cache it and refresh on 401. Returns { accessToken, expiresAt }.
Documented attack patterns abuse exactly the kind of access refresh_access_token gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for refresh_access_token:
{
"version": "1",
"default": "deny",
"tools": {
"refresh_access_token": {
"limits": [
{
"counter": "refresh_access_token_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
}refresh_access_token gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Mint a fresh short-lived access-token from the partner api-secret. Some Partner API tiers require this token (sent as the access-token header) on order/user endpoints. The token is short-lived (~minutes); cache it and refresh on 401. Returns { accessToken, expiresAt }. It is categorised as a Other tool in the Mcp Ap2 MCP Server, which means it performs auxiliary operations.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for refresh_access_token: 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 Mcp Ap2. Nothing to install.
refresh_access_token is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the refresh_access_token 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 refresh_access_token. 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.
refresh_access_token is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.