List configured Jira instances and their config_id values.
AI agents call list_configs to retrieve information from Simple Jira MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves configuration metadata about registered Jira instances. It has no side effects, does not execute code or modify data, and does not access sensitive user data beyond configuration identifiers. The blast radius of misuse is minimal—an agent could learn which Jira instances are available, but cannot act on that information without additional tools like search_issues or create_issue.
From the tool's definition Tool name 'list_configs' and description 'List configured Jira instances and their config_id values' indicates a query/retrieval operation with no modification or execution of external operations.
Attacks that exploit this kind of access
List configured Jira instances and their config_id values. It is categorised as a Read tool in the Simple Jira MCP MCP Server, which means it retrieves data without modifying state.
Register the Simple Jira MCP server in PolicyLayer and add a rule for list_configs: 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 Simple Jira MCP. Nothing to install.
list_configs 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 list_configs 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 list_configs. 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.
list_configs is provided by the Simple Jira MCP server (timohaa/simple-jira-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 →