query_dci_teams
AI agents call query_dci_teams to retrieve information from DCI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'query_' prefix strongly indicates a read operation that retrieves team data without side effects. No evidence of write, execute, destructive, or financial operations. Lower confidence (0.85 rather than higher) due to empty description, but the naming pattern and server purpose support Read classification. Severity is low because querying team data has minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'query_dci_teams' suggests data retrieval ('query') of team information. No description provided, but naming convention and context within DCI MCP Server (which enables extraction and analysis of jobs, components, and topics) indicates this queries…
Attacks that exploit this kind of access
query_dci_teams. It is categorised as a Read tool in the DCI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DCI MCP Server MCP server in PolicyLayer and add a rule for query_dci_teams: 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 DCI MCP Server. Nothing to install.
query_dci_teams 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 query_dci_teams 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 query_dci_teams. 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.
query_dci_teams is provided by the DCI MCP Server MCP server (redhat-community-ai-tools/dci-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 →