Get the version history of a relation from your DevFlow MCP knowledge graph memory
AI agents call get_relation_history to retrieve information from DevFlow MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves version history of relations from the knowledge graph. It queries existing data and returns information without side effects. No data is modified, created, or deleted. The read-only nature, combined with the confined scope (relation history lookup), results in low severity even if misused by an AI agent.
From the tool's definition Tool name 'get_relation_history' and description 'Get the version history of a relation' indicate retrieval of historical data without modification.
Attacks that exploit this kind of access
Get the version history of a relation from your DevFlow MCP knowledge graph memory. It is categorised as a Read tool in the DevFlow MCP MCP Server, which means it retrieves data without modifying state.
Register the DevFlow MCP server in PolicyLayer and add a rule for get_relation_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 DevFlow MCP. Nothing to install.
get_relation_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 get_relation_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 get_relation_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.
get_relation_history is provided by the DevFlow MCP server (takin-profit/devflow-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 →