get_history

A read tool on the MCP Framework Personal MCP server.

SERVERMCP Framework Personal SOURCEinggerman/mcps

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/inggerman-mcps/get-history.md

WHAT IT DOES

What get_history does on MCP Framework Personal

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

RISK

Why get_history is rated Low

This tool appears to retrieve historical economic data from the FRED database. The server's purpose is to expose indicators for querying and analysis, and 'get_history' fits the pattern of a simple data retrieval function.

From the tool's definition Tool named 'get_history' on a FRED macroeconomic indicators server with sibling tools like 'get_indicator', 'list_indicators', and 'search_indicators'. The empty description and naming pattern suggest retrieval of historical data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_history safely

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

get_history Allowed

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": {
    "get_history": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every get_history call is checked against it from then on.

FAQ

Questions about get_history

What does the get_history tool do? +

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

How do I enforce a policy on get_history? +

Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for 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 MCP Framework Personal. Nothing to install.

What risk level is get_history? +

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

Can I rate-limit get_history? +

Yes. Add a rate_limit block to the 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 get_history completely? +

Set action: deny in the PolicyLayer policy for 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 get_history? +

get_history is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Framework Personal, and thousands of servers like it.

This server

All 912 MCP Framework Personal tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

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