get_proforma_form_details
AI agents call get_proforma_form_details 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 'get_' prefix strongly indicates this is a retrieval operation with no side effects. However, confidence is lowered due to the empty description, which prevents verification of whether this retrieves form metadata or executes form processing logic. The term 'proforma form' is vague without additional context.
From the tool's definition Tool name 'get_proforma_form_details' uses the 'get' verb, suggesting data retrieval. Description is empty, providing no explicit confirmation of function or parameters.
Attacks that exploit this kind of access
get_proforma_form_details. 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_proforma_form_details: 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_proforma_form_details 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_proforma_form_details 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_proforma_form_details. 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_proforma_form_details is provided by the MCP Atlassian MCP server (sooperset/mcp-atlassian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.