List versions for a DataForge project.
AI agents call df_list_versions to retrieve information from DataForge Semantic MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves version information about DataForge projects. It performs a passive query operation with no side effects, no data modification, no execution of arbitrary operations, and no destructive actions. The blast radius of misuse is minimal—an agent could only gain visibility into project version history, which is metadata. Classified as Read with low severity and high confidence.
From the tool's definition Tool name 'df_list_versions' and description 'List versions for a DataForge project' indicate retrieval of metadata without modification. The verb 'list' is a classic read operation that queries existing data.
Attacks that exploit this kind of access
List versions for a DataForge project. It is categorised as a Read tool in the DataForge Semantic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DataForge Semantic MCP Server MCP server in PolicyLayer and add a rule for df_list_versions: 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 DataForge Semantic MCP Server. Nothing to install.
df_list_versions 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 df_list_versions 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 df_list_versions. 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.
df_list_versions is provided by the DataForge Semantic MCP Server MCP server (sgromych/dataforge-mcp-gateway). 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 →