[READ] List active extension-credit obligations (extender -> recipient vouches backed by a bonded SOL stake). Optionally filter by extender or recipient wallet (base58). Returns { extensions: [{ extender, recipient, bond_lamports }], count }. Empty on clusters where extension-registry isn't deplo...
AI agents call list_extensions to retrieve information from Swarm Tips — Aggregated AI Agent Activities without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
extender | string | null | — | Filter to extensions where this wallet is the extender (base58). |
recipient | string | null | — | Filter to extensions where this wallet is the recipient (base58). |
Parameters from the server's own tool schema.
This tool queries and lists extension-credit obligations without creating, modifying, deleting, or executing any operations. It is a passive data retrieval mechanism with no blast radius if misused by an AI agent—worst case would be information disclosure of wallet addresses and bond amounts already on-chain. No financial transactions, code execution, or destructive operations are possible.
From the tool's definition Tool name includes [READ] tag and description states 'List active extension-credit obligations'—retrieves data with no side effects. Parameters are optional filters (extender/recipient wallets) for querying existing records.
Documented attack patterns abuse exactly the kind of access list_extensions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Swarm Tips — Aggregated AI Agent Activities, and nothing reaches the server without passing your rules. This is the rule we recommend for list_extensions:
{
"version": "1",
"default": "deny",
"tools": {
"list_extensions": {}
}
}list_extensions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
[READ] List active extension-credit obligations (extender -> recipient vouches backed by a bonded SOL stake). Optionally filter by extender or recipient wallet (base58). Returns { extensions: [{ extender, recipient, bond_lamports }], count }. Empty on clusters where extension-registry isn't deployed. It is categorised as a Read tool in the Swarm Tips — Aggregated AI Agent Activities MCP Server, which means it retrieves data without modifying state.
list_extensions accepts 2 parameters: extender, recipient. The full parameter table on this page comes from the server's own tool schema.
Register the Swarm Tips — Aggregated AI Agent Activities MCP server in PolicyLayer and add a rule for list_extensions: 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 Swarm Tips — Aggregated AI Agent Activities. Nothing to install.
list_extensions 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 list_extensions 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 list_extensions. 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.
list_extensions is provided by the Swarm Tips — Aggregated AI Agent Activities MCP server (https://mcp.swarm.tips/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Swarm Tips — Aggregated AI Agent Activities, 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.
33 Swarm Tips — Aggregated AI Agent Activities tools catalogued and risk-classified — across an index of 43,000+ MCP servers.