# pressuredesk_meta

Return PressureDesk product metadata, routes, pricing, and latest snapshot id.

Agent View of the PolicyLayer registry record for `pressuredesk_meta`. HTML page: https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-meta

## Facts

- Tool: `pressuredesk_meta`
- Server: PressureDesk (`https://pressuredesk.autonomyforge.dev/mcp/http`) — https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk.md
- Homepage: https://github.com/https://pressuredesk.autonomyforge.dev/mcp/http
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- 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": "pressuredesk_meta",
    "arguments": {}
  }
}
```

## Why pressuredesk_meta is rated Low

This tool only retrieves static metadata about the PressureDesk service (product info, routes, pricing, snapshot identifiers). It has no side effects, does not modify data, execute code, or trigger external operations. It is a straightforward read/query operation consistent with the server's read-only design.

From the tool's own definition: "Tool description states it 'Return[s] PressureDesk product metadata, routes, pricing, and latest snapshot id' — purely retrieving/querying information. Server is explicitly described as 'Read-only'."

## Use case

AI agents call pressuredesk_meta to retrieve information from PressureDesk 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 PressureDesk:

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

## Other tools on PressureDesk (8)

- `pressuredesk_agent_home` — Read — https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-agent-home.md
- `pressuredesk_evaluate_tool` — Read — https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-evaluate-tool.md
- `pressuredesk_founding_access` — Read — https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-founding-access.md
- `pressuredesk_freshness` — Read — https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-freshness.md
- `pressuredesk_get_dossier` — Read — https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-get-dossier.md
- `pressuredesk_live_payment_status` — Read — https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-live-payment-status.md
- `pressuredesk_preview_latest` — Read — https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-preview-latest.md
- `pressuredesk_source_health` — Read — https://policylayer.com/tools/dev-autonomyforge-pressuredesk-pressuredesk/pressuredesk-source-health.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=dev-autonomyforge-pressuredesk-pressuredesk · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-autonomyforge-pressuredesk-pressuredesk