List available DataForge projects.
AI agents call df_list_projects 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 and enumerates existing DataForge projects without modifying, executing, or deleting any data. It is a straightforward metadata query operation typical of Read category tools. The low severity reflects minimal blast radius—listing projects reveals only structural metadata without exposing sensitive data values or enabling further actions without additional tool calls.
From the tool's definition Tool name 'df_list_projects' and description 'List available DataForge projects' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List available DataForge projects. 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_projects: 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_projects 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_projects 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_projects. 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_projects 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 →