clerk.list_m2m_tokens
List M2M tokens for a machine in a connected Clerk instance. Sensitive — returns token metadata for active machine credentials. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns M2M token summaries plus ...
This record as markdown: /tools/io-github-vee3io-vee3/clerk.list-m2m-tokens.md
What clerk.list_m2m_tokens does on Vee3
AI agents call clerk.list_m2m_tokens to retrieve information from Vee3 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 |
|---|---|---|---|
limit | object | — | Maximum number of results to return (1–500). |
offset | object | — | Number of results to skip before returning. |
expired | object | — | Include expired tokens (default false). |
revoked | object | — | Include revoked tokens (default false). |
subject | string | Yes | Machine id (mch_...) whose tokens to list. |
clerk_instance_id | object | — | Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account. |
Parameters from the server's own tool schema.
Why clerk.list_m2m_tokens is rated Low
Retrieves sensitive M2M token metadata enabling credential enumeration attacks; no modification occurs.
From the tool's definition List M2M tokens, token metadata for active machine credentials
Attacks that exploit this kind of access
The rule that runs clerk.list_m2m_tokens safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clerk.list_m2m_tokens, this is the rule to start with:
clerk.list_m2m_tokens 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 Vee3, apply this rule, and every clerk.list_m2m_tokens call is checked against it from then on.
Questions about clerk.list_m2m_tokens
List M2M tokens for a machine in a connected Clerk instance. Sensitive — returns token metadata for active machine credentials. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns M2M token summaries plus total_count. JWT-format tokens are not listed. Cost = 5 tokens. It is categorised as a Read tool in the Vee3 MCP Server, which means it retrieves data without modifying state.
clerk.list_m2m_tokens accepts 6 parameters: limit, offset, expired, revoked, subject, clerk_instance_id. Required: subject. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for clerk.list_m2m_tokens: 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 Vee3. Nothing to install.
clerk.list_m2m_tokens 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 clerk.list_m2m_tokens 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 clerk.list_m2m_tokens. 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.
clerk.list_m2m_tokens is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
This server
Across the catalogue