Get a comprehensive summary of a specific vault or all vaults if no address is provided. Retrieves a summary of all important information about a vault, including balance, positions, recent activity, and performance metrics. This provides a high-level overview of the vault's current state. Use jm...
AI agents call paradex_vault_summary to retrieve information from Paradex MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Limit the number of results to the specified number. |
offset | integer | — | Offset the results to the specified number. |
vault_address | string | — | The address of the vault to get summary for or None to get all vaults. |
jmespath_filter | string | — | JMESPath expression to filter or transform the result. |
Parameters from the server's own tool schema.
This is a read-only data retrieval tool that queries vault information. While the severity is elevated to medium (rather than low) because vault data is sensitive financial information that could inform harmful trading decisions if misused by an AI agent, the tool itself only reads existing data.
From the tool's definition Tool retrieves and queries vault data including 'balance, positions, recent activity, and performance metrics' with no modification, creation, or deletion capabilities.
Documented attack patterns abuse exactly the kind of access paradex_vault_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Paradex MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for paradex_vault_summary:
{
"version": "1",
"default": "deny",
"tools": {
"paradex_vault_summary": {}
}
}paradex_vault_summary 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.
Get a comprehensive summary of a specific vault or all vaults if no address is provided. Retrieves a summary of all important information about a vault, including balance, positions, recent activity, and performance metrics. This provides a high-level overview of the vault's current state. Use jmespath_filter to reduce the number of results as much as possible as number of vaults can be large. You can use JMESPath expressions to filter, sort, or transform the results. Examples: - Filter by TVL: "[?to_number(tvl) > 10000]" - Filter by performance: "[?to_number(total_roi) > 5.0]" - Sort by TVL (descending): "reverse(sort_by([*], &to_number(tvl)))" - Get top performers: "sort_by([*], &to_number(total_roi))[-3:]" - Filter by recent returns: "[?to_number(roi_24h) > 0.5]" - Extract specific metrics: "[*].{address: address, tvl: tvl, total_roi: total_roi, volume_24h: volume_24h}". It is categorised as a Read tool in the Paradex MCP Server MCP Server, which means it retrieves data without modifying state.
paradex_vault_summary accepts 4 parameters: limit, offset, vault_address, jmespath_filter. The full parameter table on this page comes from the server's own tool schema.
Register the Paradex MCP Server MCP server in PolicyLayer and add a rule for paradex_vault_summary: 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 Paradex MCP Server. Nothing to install.
paradex_vault_summary 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 paradex_vault_summary 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 paradex_vault_summary. 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.
paradex_vault_summary is provided by the Paradex MCP Server MCP server (tradeparadex/mcp-paradex-py). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Paradex MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Paradex MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.