Returns available Jira projects and keys.
AI agents call get_jira_context to retrieve information from Enterprise AI Bridge (MCP) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static information about available Jira projects and their identifiers. It performs a query operation without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an agent could only discover which projects exist, which is typically non-sensitive metadata in an enterprise context. Classification as Read is appropriate.
From the tool's definition Tool name 'get_jira_context' and description 'Returns available Jira projects and keys' indicate a retrieval operation that queries and lists metadata with no side effects.
Attacks that exploit this kind of access
Returns available Jira projects and keys. It is categorised as a Read tool in the Enterprise AI Bridge (MCP) MCP Server, which means it retrieves data without modifying state.
Register the Enterprise AI Bridge (MCP) MCP server in PolicyLayer and add a rule for get_jira_context: 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 Enterprise AI Bridge (MCP). Nothing to install.
get_jira_context 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_jira_context 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_jira_context. 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_jira_context is provided by the Enterprise AI Bridge (MCP) MCP server (olegvasilievcs/mcp-server). 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 →