Search for Jira filters by name.
AI agents call search_jira_filters 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.
This tool performs a read-only lookup operation against Jira filters. It retrieves information about existing filters based on a search criterion (name) but does not create, modify, delete, or execute any actions. The blast radius of misuse is minimal—an agent could at worst discover filters it shouldn't know about, but cannot modify systems or access unauthorized data through this tool alone.
From the tool's definition Tool name is 'search_jira_filters' and description states 'Search for Jira filters by name.' The verb 'search' combined with 'by name' indicates a query operation that retrieves filter metadata without modifying any data.
Attacks that exploit this kind of access
Search for Jira filters by name. 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 search_jira_filters: 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.
search_jira_filters 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 search_jira_filters 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 search_jira_filters. 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.
search_jira_filters 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 →