List uploaded job inputs for the authenticated account, including mount paths.
AI agents call list_job_inputs to retrieve information from Jungle Grid without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists data (job inputs and their metadata) belonging to the authenticated user. It performs no modifications, deletions, code execution, or financial operations. The only information exposed is mount paths and job input metadata, which represents a low-severity read-only disclosure. Confidence is high because the description explicitly indicates a listing/retrieval operation.
From the tool's definition Tool name 'list_job_inputs' and description 'List uploaded job inputs for the authenticated account, including mount paths' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List uploaded job inputs for the authenticated account, including mount paths. It is categorised as a Read tool in the Jungle Grid MCP Server, which means it retrieves data without modifying state.
Register the Jungle Grid MCP server in PolicyLayer and add a rule for list_job_inputs: 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 Jungle Grid. Nothing to install.
list_job_inputs 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_job_inputs 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_job_inputs. 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_job_inputs is provided by the Jungle Grid MCP server (jungle-grid/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 →