# list_profiles

List Forge vaults (Core/Middle/Infra) and agent strategies (Conservative/Balanced/Aggressive). Mainnet: Core and Middle vaults live; conservative and balanced strategies live.

Agent View of the PolicyLayer registry record for `list_profiles`. HTML page: https://policylayer.com/tools/com-forgetreasury-treasury/list-profiles

## Facts

- Tool: `list_profiles`
- Server: Forge Treasury (`https://mcp.forgetreasury.com/mcp`) — https://policylayer.com/tools/com-forgetreasury-treasury.md
- Homepage: https://github.com/forge-treasury/forge-cursor-plugin
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_profiles",
    "arguments": {}
  }
}
```

## Why list_profiles is rated Low

This tool queries and displays available vault and strategy configurations. It is purely informational, returning structured data about existing infrastructure without altering state, executing code, or moving funds. The low severity reflects minimal blast radius: an AI agent cannot cause damage by calling this read-only endpoint.

From the tool's own definition: "Tool name is 'list_profiles' and description states 'List Forge vaults' and 'agent strategies' — a retrieval operation with no side effects. No modification, deletion, execution, or financial transaction occurs."

## Use case

AI agents call list_profiles to retrieve information from Forge Treasury without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Forge Treasury:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_profiles": {}
  }
}
```

## Other tools on Forge Treasury (8)

- `claim_forge` — Financial — https://policylayer.com/tools/com-forgetreasury-treasury/claim-forge.md
- `deposit` — Financial — https://policylayer.com/tools/com-forgetreasury-treasury/deposit.md
- `withdraw` — Financial — https://policylayer.com/tools/com-forgetreasury-treasury/withdraw.md
- `get_balance` — Read — https://policylayer.com/tools/com-forgetreasury-treasury/get-balance.md
- `get_current_apy` — Read — https://policylayer.com/tools/com-forgetreasury-treasury/get-current-apy.md
- `get_forge_rewards` — Read — https://policylayer.com/tools/com-forgetreasury-treasury/get-forge-rewards.md
- `get_vault_stats` — Read — https://policylayer.com/tools/com-forgetreasury-treasury/get-vault-stats.md
- `simulate_deposit` — Read — https://policylayer.com/tools/com-forgetreasury-treasury/simulate-deposit.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-forgetreasury-treasury · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-forgetreasury-treasury