AI agents call search_confluence_pages_by_title 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 that retrieve page data are Read category—they query and return information without side effects. The tool appears to filter existing Confluence pages by title, consistent with other get/search tools on the server. Severity is low because exposing page title search carries minimal risk; an agent can only discover existing page metadata.
From the tool's definition Tool name 'search_confluence_pages_by_title' indicates a search/query operation. No description provided, but naming convention and sibling tools (get_confluence_pages, get_confluence_spaces) suggest this retrieves data without modification.
Documented attack patterns abuse exactly the kind of access search_confluence_pages_by_title gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Atlassian, and nothing reaches the server without passing your rules. This is the rule we recommend for search_confluence_pages_by_title:
{
"version": "1",
"default": "deny",
"tools": {
"search_confluence_pages_by_title": {}
}
}search_confluence_pages_by_title is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
search_confluence_pages_by_title. 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_confluence_pages_by_title: 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_confluence_pages_by_title 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_confluence_pages_by_title 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_confluence_pages_by_title. 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_confluence_pages_by_title is provided by the MCP Atlassian MCP server (samwang0723/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Atlassian, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 MCP Atlassian tools catalogued and risk-classified — across an index of 43,000+ MCP servers.