list_jobs
AI agents call list_jobs to retrieve information from NGS360 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's name 'list_jobs' clearly denotes querying/listing existing job records without side effects or data modification. Even without a description, this is a standard read operation typical of bioinformatics workflow platforms. The confidence is moderate due to the empty description, but the semantic meaning of 'list' strongly indicates a Read category tool with low severity impact.
From the tool's definition Tool name 'list_jobs' indicates a retrieval operation with no modification capability. The absence of a description lowers confidence slightly, but the naming convention is consistent with other Read category tools (e.g., 'browse_s3') on this bioinformatics…
Attacks that exploit this kind of access
list_jobs. It is categorised as a Read tool in the NGS360 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the NGS360 MCP Server MCP server in PolicyLayer and add a rule for list_jobs: 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 NGS360 MCP Server. Nothing to install.
list_jobs 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_jobs 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_jobs. 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_jobs is provided by the NGS360 MCP Server MCP server (ngs360/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 →