List D-Tools SI product catalog entries with optional pagination and search text filtering.
AI agents call list_catalogs to retrieve information from D-Tools 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 queries catalog entries from the D-Tools system with search and pagination capabilities. It does not create, modify, delete, or execute operations—it only fetches and displays existing data. This is a classic Read operation with minimal security risk.
From the tool's definition Tool name 'list_catalogs' and description 'List D-Tools SI product catalog entries with optional pagination and search text filtering' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List D-Tools SI product catalog entries with optional pagination and search text filtering. It is categorised as a Read tool in the D-Tools MCP Server MCP Server, which means it retrieves data without modifying state.
Register the D-Tools MCP Server MCP server in PolicyLayer and add a rule for list_catalogs: 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 D-Tools MCP Server. Nothing to install.
list_catalogs 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_catalogs 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_catalogs. 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_catalogs is provided by the D-Tools MCP Server MCP server (saml1211/d-tools-mcp-server). 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 →