list_all_classes
AI agents call list_all_classes to retrieve information from IBM Content Services MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or query class definitions from IBM FileNet Content Manager, which is a read-only operation with no side effects. While the description is empty (lowering confidence slightly), the name 'list_all_classes' strongly suggests data retrieval. Even if misused by an AI agent, listing classes would only expose metadata/schema information, not sensitive document content or destructive actions.
From the tool's definition Tool name 'list_all_classes' indicates a listing/query operation that retrieves class definitions or metadata. The lack of description and the naming convention suggest enumeration of available content classes without modification or execution.
Attacks that exploit this kind of access
list_all_classes. It is categorised as a Read tool in the IBM Content Services MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IBM Content Services MCP Server MCP server in PolicyLayer and add a rule for list_all_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 IBM Content Services MCP Server. Nothing to install.
list_all_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 list_all_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 list_all_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.
list_all_classes is provided by the IBM Content Services MCP Server MCP server (mohamedarif-m/filenet-mcp-localfile). 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 →