count_jira_tickets
AI agents call count_jira_tickets 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 tool appears to query Jira for ticket count data without modifying, deleting, or executing operations. Counting is a retrieval operation consistent with the Read category. Confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity about whether additional side effects might occur; however, the name strongly implies a simple aggregation query.
From the tool's definition Tool name 'count_jira_tickets' suggests a counting/aggregation operation that retrieves ticket statistics from Jira. No description provided, but 'count' operations are non-modifying read-only queries.
Attacks that exploit this kind of access
count_jira_tickets. 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 count_jira_tickets: 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.
count_jira_tickets 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 count_jira_tickets 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 count_jira_tickets. 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.
count_jira_tickets 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 →