AI agents call filters.getFilter to retrieve information from Gojira without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves an existing filter configuration from Jira by its identifier. It performs a query operation without altering data, executing code, or triggering external actions. The action is read-only and non-destructive, fitting squarely into the Read category. Severity is low because accessing filter metadata poses minimal risk; filters are typically non-sensitive configuration objects.
From the tool's definition Tool name 'getFilter' and description 'Get a filter by id' indicate a retrieval operation with no modification or execution of side effects.
Attacks that exploit this kind of access
Get a filter by id. It is categorised as a Read tool in the Gojira MCP Server, which means it retrieves data without modifying state.
Register the Gojira MCP server in PolicyLayer and add a rule for filters.getFilter: 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 Gojira. Nothing to install.
filters.getFilter 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 filters.getFilter 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 filters.getFilter. 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.
filters.getFilter is provided by the Gojira MCP server (windoze95/gojira-mcp). 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 →