Get detailed information about a specific vault or all vaults if no address is provided. Retrieves comprehensive details about a specific vault identified by its address, including configuration, permissions, and other vault-specific parameters. Use jmespath_filter to reduce the number of results...
AI agents call paradex_vaults 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 details for or empty string to get all vaults. |
jmespath_filter | string | — | JMESPath expression to filter, sort, or limit the results. |
Parameters from the server's own tool schema.
This tool retrieves and queries vault data without modifying, deleting, executing commands, or moving financial assets. While it relates to a trading platform and vaults may contain financial assets, the tool itself only reads vault information—it does not execute trades, transfer funds, or commit financial obligations.
From the tool's definition Tool description states 'Get detailed information about a specific vault or all vaults' and 'Retrieves comprehensive details about a specific vault...including configuration, permissions, and other vault-specific parameters.' The tool uses JMESPath…
Documented attack patterns abuse exactly the kind of access paradex_vaults 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_vaults:
{
"version": "1",
"default": "deny",
"tools": {
"paradex_vaults": {}
}
}paradex_vaults 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 detailed information about a specific vault or all vaults if no address is provided. Retrieves comprehensive details about a specific vault identified by its address, including configuration, permissions, and other vault-specific parameters. 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 limit the results. Examples: - Filter by owner: "[?owner_account=='0x123...']" - Filter by status: "[?status=='ACTIVE']" - Find vaults with specific strategy: "[?contains(strategies, 'strategy_id')]" - Sort by creation date: "sort_by([*], &created_at)" - Limit to newest vaults: "sort_by([*], &created_at)[-5:]" - Select specific fields: "[*].{address: address, name: name, kind: kind, status: status}". It is categorised as a Read tool in the Paradex MCP Server MCP Server, which means it retrieves data without modifying state.
paradex_vaults 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_vaults: 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_vaults 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_vaults 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_vaults. 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_vaults 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.