[DEPRECATED] List all available classes in DEXPI or SFILES schemas. Use schema_query(operation=
AI agents call schema_list_classes 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 retrieves or enumerates metadata about available schema classes without creating, modifying, deleting, or executing any side effects. The deprecation notice and suggestion to use schema_query does not change its fundamental read-only nature.
From the tool's definition Tool name 'schema_list_classes' and description 'List all available classes in DEXPI or SFILES schemas' indicate a query/retrieval operation with no data modification capability.
Documented attack patterns abuse exactly the kind of access schema_list_classes 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 schema_list_classes:
{
"version": "1",
"default": "deny",
"tools": {
"schema_list_classes": {}
}
} schema_list_classes 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.
[DEPRECATED] List all available classes in DEXPI or SFILES schemas. Use schema_query(operation=. 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 schema_list_classes: 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.
schema_list_classes 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 schema_list_classes 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 schema_list_classes. 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.
schema_list_classes 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.