TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER
Gets API token metadata for a Trello member; actual token values are excluded for security.
This record as markdown: /tools/trello/trello-get-members-tokens-by-id-member.md
What TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER does on Trello
AI agents call TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER to retrieve information from Trello 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 |
|---|---|---|---|
filter | string | — | Filters the list of tokens. Use 'all' to retrieve all tokens or 'none' to retrieve no tokens. |
idMember | string | — | The ID or username of the Trello member for whom to retrieve token information. |
Parameters from the server's own tool schema.
Why TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER is rated Low
This tool retrieves metadata about API tokens (such as creation date, last used, name, or scope) without exposing the actual secret token values. It is a read-only query operation with no side effects. The exclusion of actual token values significantly reduces risk, as it prevents disclosure of sensitive credentials. The blast radius is limited to information disclosure of token metadata, which is low-severity.
From the tool's definition Gets API token metadata for a Trello member; actual token values are excluded for security.
Attacks that exploit this kind of access
The rule that runs TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trello, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER, this is the rule to start with:
TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER 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 Trello, apply this rule, and every TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER call is checked against it from then on.
Questions about TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER
Gets API token metadata for a Trello member; actual token values are excluded for security. It is categorised as a Read tool in the Trello MCP Server, which means it retrieves data without modifying state.
TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER accepts 2 parameters: filter, idMember. The full parameter table on this page comes from the server's own tool schema.
Register the Trello MCP server in PolicyLayer and add a rule for TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER: 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 Trello. Nothing to install.
TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER 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 TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER 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 TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER. 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.
TRELLO_GET_MEMBERS_TOKENS_BY_ID_MEMBER is provided by the Trello MCP server (mcp-server-trello). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trello, and thousands of servers like it.
This server
Across the catalogue