# get_transaction

Get detailed information about a specific transaction.

Agent View of the PolicyLayer registry record for `get_transaction`. HTML page: https://policylayer.com/tools/com-zype-mcp-server/get-transaction

## Facts

- Tool: `get_transaction`
- Server: Zype Com (`zype/zype-mcp`) — https://policylayer.com/tools/com-zype-mcp-server.md
- Homepage: https://github.com/zype/zype-mcp
- Risk category: Read (Low risk)
- Registry record: grade F, identity verified
- Server auth posture: gated_ambiguous
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `transaction_id` | string | yes | The transaction ID |

Parameters from the server's own tool schema.

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_transaction",
    "arguments": {
      "transaction_id": "<transaction_id>"
    }
  }
}
```

## Why get_transaction is rated Low

This tool queries and retrieves existing transaction details without creating, modifying, deleting, or executing any operations. It is a read-only operation with no side effects. The low severity reflects that financial data exposure is concerning but this tool itself does not move money, create obligations, or alter state.

From the tool's own definition: "Tool name and description indicate retrieval of transaction data: 'Get detailed information about a specific transaction.' No modification, deletion, or execution is performed."

## Use case

AI agents call get_transaction to retrieve information from Zype Com 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 Zype Com:

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

## Other tools on Zype Com (295)

- `cancel_subscription` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/cancel-subscription.md
- `delete_ad_tag` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-ad-tag.md
- `delete_ad_timing` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-ad-timing.md
- `delete_category` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-category.md
- `delete_consumer` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-consumer.md
- `delete_content_rule_group` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-content-rule-group.md
- `delete_content_rule_profile` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-content-rule-profile.md
- `delete_live_encoder` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-live-encoder.md
- `delete_live_event` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-live-event.md
- `delete_plan` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-plan.md
- `delete_playlist` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-playlist.md
- `delete_playlist_entitlement` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-playlist-entitlement.md
- `delete_program_guide` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-program-guide.md
- `delete_redemption_code` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-redemption-code.md
- `delete_segment` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-segment.md
- `delete_self_hosted_source` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-self-hosted-source.md
- `delete_subscription` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-subscription.md
- `delete_subtitle` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-subtitle.md
- `delete_subtitle_playlist` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-subtitle-playlist.md
- `delete_transaction` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-transaction.md
- `delete_video` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video.md
- `delete_video_entitlement` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video-entitlement.md
- `delete_video_favorite` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video-favorite.md
- `delete_video_source` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-video-source.md
- `delete_zobject` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-zobject.md
- `delete_zobject_type` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/delete-zobject-type.md
- `playout_delete_ad_timing` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-ad-timing.md
- `playout_delete_all_ad_timings` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-all-ad-timings.md
- `playout_delete_block` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-block.md
- `playout_delete_channel` — Destructive — https://policylayer.com/tools/com-zype-mcp-server/playout-delete-channel.md
- …and 265 more: https://policylayer.com/tools/com-zype-mcp-server.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-zype-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-zype-mcp-server