List recent generation history.
AI agents call list_history to retrieve information from PixelForge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data about image generations. It performs a read-only query of existing records with no side effects, no code execution, no data modification, and no destructive actions. The blast radius of misuse is minimal—an agent could retrieve generation history it shouldn't access, but cannot alter or delete records or trigger new operations.
From the tool's definition Tool name 'list_history' and description 'List recent generation history' indicate a retrieval operation that queries past generation records without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
List recent generation history. It is categorised as a Read tool in the PixelForge MCP MCP Server, which means it retrieves data without modifying state.
Register the PixelForge MCP server in PolicyLayer and add a rule for list_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 PixelForge MCP. Nothing to install.
list_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_history is provided by the PixelForge MCP server (tehnolabs/pixelforge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →