export_routing_history

Exporta el historial en JSON o CSV. Parametros: format (

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/export-routing-history.md

WHAT IT DOES

What export_routing_history does on MCP Framework Personal

AI agents call export_routing_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 export_routing_history is rated Low

The tool exports/reads historical routing data without modifying or deleting anything. It retrieves existing records and serializes them to JSON or CSV. Low severity as it only reads history data, though the description is truncated which slightly lowers confidence.

From the tool's definition Exporta el historial en JSON o CSV — exports history data in JSON or CSV format

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs export_routing_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 export_routing_history, this is the rule to start with:

export_routing_history Allowed

export_routing_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": {
    "export_routing_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 export_routing_history call is checked against it from then on.

FAQ

Questions about export_routing_history

What does the export_routing_history tool do? +

Exporta el historial en JSON o CSV. Parametros: format (. 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 export_routing_history? +

Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for export_routing_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 export_routing_history? +

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

Can I rate-limit export_routing_history? +

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

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

export_routing_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 811 MCP Framework Personal tools →

Across the catalogue

The MCP Attack Database →

Guides

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