get_access_token
AI agents call get_access_token to retrieve information from GreenNode MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, 'get_access_token' most naturally classifies as a Read operation—it retrieves an authentication token for subsequent API calls. While tokens are sensitive, the tool itself does not modify infrastructure, execute commands, or cause destructive changes. In credential/token management contexts, retrieval is typically Read unless the tool also grants new privileges or delegates access.
From the tool's definition Tool name 'get_access_token' indicates token retrieval; description is empty, limiting confidence. Sibling tools suggest infrastructure management context where access tokens are credentials used for authentication rather than secrets management.
Attacks that exploit this kind of access
get_access_token. It is categorised as a Read tool in the GreenNode MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GreenNode MCP Server MCP server in PolicyLayer and add a rule for get_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 GreenNode MCP Server. Nothing to install.
get_access_token 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 get_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 get_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.
get_access_token is provided by the GreenNode MCP Server MCP server (vngcloud/greennode-mcp). 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 →