AI agents call project_list to retrieve information from Engineering MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing models without creating, modifying, or deleting any data. The verb 'list' is a quintessential read operation. The blast radius is minimal—an AI agent invoking this tool can only discover what models exist in a project, posing no risk of unintended data modification or resource consumption beyond normal query costs.
From the tool's definition Tool name 'project_list' and description 'List all models in a project' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access project_list gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Engineering MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for project_list:
{
"version": "1",
"default": "deny",
"tools": {
"project_list": {}
}
}project_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all models in a project. It is categorised as a Read tool in the Engineering MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Engineering MCP Server MCP server in PolicyLayer and add a rule for project_list: 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 Engineering MCP Server. Nothing to install.
project_list 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 project_list 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 project_list. 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.
project_list is provided by the Engineering MCP Server MCP server (puran-water/dexpi-sfiles-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Engineering MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
72 Engineering MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.