browse_directory
AI agents call browse_directory to retrieve information from MCP Atlassian + Bitbucket without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name suggests retrieving/querying directory structure with no side effects. Confidence is moderate (0.6) rather than high because the description is empty and we cannot verify the exact scope of what 'directory' refers to (Bitbucket repository structure, Confluence space hierarchy, etc.) or whether it has any filtering/access control implications.
From the tool's definition Tool name 'browse_directory' indicates a read operation for listing or exploring directory contents, consistent with other Read tools on this server (get_all_projects, get_attachments, get_agile_boards).
Attacks that exploit this kind of access
browse_directory. It is categorised as a Read tool in the MCP Atlassian + Bitbucket MCP Server, which means it retrieves data without modifying state.
Register the MCP Atlassian + Bitbucket MCP server in PolicyLayer and add a rule for browse_directory: 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 + Bitbucket. Nothing to install.
browse_directory 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 browse_directory 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 browse_directory. 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.
browse_directory is provided by the MCP Atlassian + Bitbucket MCP server (jellythomas/mcp-atlassian-with-bitbucket). 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 →