get_field_options
AI agents call get_field_options 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 indicates data retrieval. The tool retrieves field options (likely configuration or dropdown values) from Jira/Confluence without side effects. Although the description is empty, the naming pattern and context of sibling read-only tools strongly suggest this is a query/retrieval operation. No creation, modification, deletion, or external execution is indicated.
From the tool's definition Tool name 'get_field_options' and sibling tools like 'get_attachments', 'get_comments', 'get_all_projects', 'get_board_issues' which are clearly read operations retrieving data without modification.
Attacks that exploit this kind of access
get_field_options. 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_field_options: 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_field_options 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_field_options 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_field_options. 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_field_options is provided by the MCP Atlassian MCP server (lklkxcxc/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 →