search_code
AI agents call search_code to retrieve information from Mcp Atlassian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Search operations are read-only with no data modification or side effects. The tool retrieves or queries code data without creating, modifying, deleting, or executing anything. Severity is low due to limited blast radius—worst case is exposure of searchable code content. Confidence is 0.85 (not higher) because the description is empty, relying on contextual inference from the tool name and sibling tools.
From the tool's definition Tool name 'search_code' combined with server context describing search functionality for Confluence and Jira. The sibling tools include multiple 'get_' and 'download_' operations, establishing a pattern of read-only data retrieval on this server.
Attacks that exploit this kind of access
search_code. It is categorised as a Read tool in the Mcp Atlassian MCP Server, which means it retrieves data without modifying state.
Register the Mcp Atlassian MCP server in PolicyLayer and add a rule for search_code: 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 Mcp Atlassian. Nothing to install.
search_code 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_code 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_code. 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_code is provided by the Mcp Atlassian MCP server (voarsh2/mcp-atlassian). 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 →