read_migration_history

A read tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

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/io-github-devopam-mcpg/read-migration-history.md

WHAT IT DOES

What read_migration_history does on Mcpg

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

RISK

Why read_migration_history is rated Low

The tool name clearly indicates a read-only operation that retrieves migration history records from the PostgreSQL database. No side effects are described or implied. The 'read' prefix in the function name directly signals a query/retrieval operation without create, update, delete, or execute semantics.

From the tool's definition Tool name 'read_migration_history' explicitly uses 'read' prefix and 'history' suffix, indicating retrieval of historical data with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_migration_history safely

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

read_migration_history Allowed

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

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

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

FAQ

Questions about read_migration_history

What does the read_migration_history tool do? +

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

How do I enforce a policy on read_migration_history? +

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

What risk level is read_migration_history? +

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

Can I rate-limit read_migration_history? +

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

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

read_migration_history is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools →

Across the catalogue

claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

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