get_scenario_list
AI agents call get_scenario_list to retrieve information from Jenkins MCP Tool without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to retrieve or enumerate scenario data with no side effects. The 'get_' prefix and its position among other Read-category tools (get_build_log, get_build_status, get_job_parameters, get_server_names) confirms it performs data retrieval. Confidence is slightly reduced due to empty description, but naming and context are strong indicators of a harmless read operation.
From the tool's definition Tool name 'get_scenario_list' and sibling context indicate a retrieval operation. Description is empty, but naming convention and placement among query tools (get_build_log, get_build_status, get_job_parameters, get_server_names, search_jobs) strongly suggest…
Attacks that exploit this kind of access
get_scenario_list. It is categorised as a Read tool in the Jenkins MCP Tool MCP Server, which means it retrieves data without modifying state.
Register the Jenkins MCP Tool MCP server in PolicyLayer and add a rule for get_scenario_list: 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 Jenkins MCP Tool. Nothing to install.
get_scenario_list 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_scenario_list 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_scenario_list. 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_scenario_list is provided by the Jenkins MCP Tool MCP server (xhuaustc/jenkins-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 →