get_page_views
AI agents call get_page_views 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.
The tool name 'get_page_views' indicates retrieval of view statistics or metadata about Confluence pages—a read-only query with no side effects. Even without an explicit description, the naming pattern and server context (interaction with Atlassian Confluence/Jira) strongly suggest this retrieves analytics or metadata rather than modifying or executing anything.
From the tool's definition Tool name 'get_page_views' and server context indicating read/retrieval operations. Description is empty, but sibling tools on this server include primarily read operations (get_*, download_*, batch_get_*) and the server enables searching and querying…
Attacks that exploit this kind of access
get_page_views. 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 get_page_views: 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.
get_page_views 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 get_page_views 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 get_page_views. 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.
get_page_views 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 →