retrieve_consumer_access_token
Get a CONSUMER access token from the api.zype.com authorization server, via password or refresh_token grant. This is the end-user token, not the admin token issued by login.zype.com.
This record as markdown: /tools/com-zype-mcp-server/retrieve-consumer-access-token.md
What retrieve_consumer_access_token does on Zype Com
AI agents call retrieve_consumer_access_token to retrieve information from Zype Com without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
pin | string | — | Device pin |
password | string | — | Consumer password |
username | string | — | Consumer email; required with grant_type=password |
client_id | string | Yes | Client ID (required) |
grant_type | string | Yes | Grant type (required) |
client_secret | string | Yes | Client secret (required) |
refresh_token | string | — | Refresh token; required with grant_type=refresh_token |
linked_device_id | string | — | Linked device ID (needs pin) |
Parameters from the server's own tool schema.
Why retrieve_consumer_access_token is rated Low
Even though retrieve_consumer_access_token only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHandles credentials or secrets (password) · Admin/system-level operation
Attacks that exploit this kind of access
The rule that runs retrieve_consumer_access_token safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Zype Com, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For retrieve_consumer_access_token, this is the rule to start with:
retrieve_consumer_access_token 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 Zype Com, apply this rule, and every retrieve_consumer_access_token call is checked against it from then on.
Questions about retrieve_consumer_access_token
Get a CONSUMER access token from the api.zype.com authorization server, via password or refresh_token grant. This is the end-user token, not the admin token issued by login.zype.com. It is categorised as a Read tool in the Zype Com MCP Server, which means it retrieves data without modifying state.
retrieve_consumer_access_token accepts 8 parameters: pin, password, username, client_id, grant_type, client_secret, refresh_token, linked_device_id. Required: client_id, grant_type, client_secret. The full parameter table on this page comes from the server's own tool schema.
Register the Zype Com MCP server in PolicyLayer and add a rule for retrieve_consumer_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 Zype Com. Nothing to install.
retrieve_consumer_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 retrieve_consumer_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 retrieve_consumer_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.
retrieve_consumer_access_token is provided by the Zype Com MCP server (zype/zype-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Zype Com, and thousands of servers like it.
This server
Across the catalogue