pine_get_history

A read tool on the Pine Assistant MCP server.

SERVERPine Assistant MCP Server SOURCE19pine-ai/pine-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/19pine-ai-pine-mcp-server/pine-get-history.md

WHAT IT DOES

What pine_get_history does on Pine Assistant MCP Server

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.

RISK

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 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…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pine_get_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Pine Assistant MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For pine_get_history, this is the rule to start with:

pine_get_history Allowed

pine_get_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Pine Assistant MCP Server, apply this rule, and every pine_get_history call is checked against it from then on.

FAQ

Questions about pine_get_history

What does the pine_get_history tool do? +

pine_get_history is a read tool on the Pine Assistant MCP Server MCP server. It is categorised as a Read tool in the Pine Assistant MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pine_get_history? +

Register the Pine Assistant MCP Server MCP server in PolicyLayer and add a rule for pine_get_history: 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 Pine Assistant MCP Server. Nothing to install.

What risk level is pine_get_history? +

pine_get_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pine_get_history? +

Yes. Add a rate_limit block to the pine_get_history 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.

How do I block pine_get_history completely? +

Set action: deny in the PolicyLayer policy for pine_get_history. 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.

What MCP server provides pine_get_history? +

pine_get_history is provided by the Pine Assistant MCP Server MCP server (19pine-ai/pine-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Pine Assistant MCP Server, and thousands of servers like it.

This server

All 19 Pine Assistant MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →