Get image generation/editing history for a specific image. See all operations performed on an image.
AI agents call mlimg_get_history to retrieve information from FluentCommunity Manager without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries historical information about image operations without creating, modifying, deleting, or executing any operations. It is a pure read operation that returns audit/history information about a specific image's processing history.
From the tool's definition Tool name 'mlimg_get_history' and description 'Get image generation/editing history for a specific image. See all operations performed on an image.' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
Get image generation/editing history for a specific image. See all operations performed on an image. It is categorised as a Read tool in the FluentCommunity Manager MCP Server, which means it retrieves data without modifying state.
Register the FluentCommunity Manager MCP server in PolicyLayer and add a rule for mlimg_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 FluentCommunity Manager. Nothing to install.
mlimg_get_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 mlimg_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.
Set action: deny in the PolicyLayer policy for mlimg_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.
mlimg_get_history is provided by the FluentCommunity Manager MCP server (wplaunchify/fluent-community-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 →