# pine_get_history

A read tool on the Pine Assistant MCP Server MCP server.

Agent View of the PolicyLayer registry record for `pine_get_history`. HTML page: https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-get-history

## Facts

- Tool: `pine_get_history`
- Server: Pine Assistant MCP Server (`19pine-ai/pine-mcp-server`) — https://policylayer.com/tools/19pine-ai-pine-mcp-server.md
- Homepage: https://github.com/19PINE-AI/pine-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- 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": "pine_get_history",
    "arguments": {}
  }
}
```

## Why pine_get_history is rated Low

The 'get_history' naming pattern is a strong indicator of a Read operation that queries and retrieves data without modifying it. However, confidence is moderate because the description is absent and the tool could potentially expose sensitive financial or personal conversation history related to billing and subscription management.

From the tool's own definition: "Tool name 'pine_get_history' indicates retrieval of historical data. The description is empty, but based on the sibling tools and server purpose (managing Pine AI tasks including bills, subscriptions, disputes, and calls), this likely retrieves past…"

## Use case

AI agents call pine_get_history to retrieve information from Pine Assistant MCP Server 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 Pine Assistant MCP Server:

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

## Other tools on Pine Assistant MCP Server (18)

- `pine_delete_attachment` — Destructive — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-delete-attachment.md
- `pine_session_delete` — Destructive — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-session-delete.md
- `pine_send_auth_confirmation` — Execute — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-send-auth-confirmation.md
- `pine_send_form_response` — Execute — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-send-form-response.md
- `pine_send_message` — Execute — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-send-message.md
- `pine_session_create` — Execute — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-session-create.md
- `pine_task_stop` — Execute — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-task-stop.md
- `pine_task_start` — Financial — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-task-start.md
- `pine_session_get` — Read — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-session-get.md
- `pine_session_list` — Read — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-session-list.md
- `pine_session_url` — Read — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-session-url.md
- `pine_auth_request_code` — Write — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-auth-request-code.md
- `pine_auth_verify_code` — Write — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-auth-verify-code.md
- `pine_send_location_response` — Write — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-send-location-response.md
- `pine_send_location_selection` — Write — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-send-location-selection.md
- `pine_social_share` — Write — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-social-share.md
- `pine_update_call_reminder` — Write — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-update-call-reminder.md
- `pine_upload_attachment` — Write — https://policylayer.com/tools/19pine-ai-pine-mcp-server/pine-upload-attachment.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=19pine-ai-pine-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/19pine-ai-pine-mcp-server