list_oke_work_requests
AI agents call list_oke_work_requests to retrieve information from OCI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries data about OKE work requests without modifying them. While the description is empty, the naming convention and sibling context strongly indicate a read operation. Severity is medium rather than low because work request status could reveal operational details about infrastructure changes, which might inform further attacks, but the tool itself causes no side effects.
From the tool's definition Tool name 'list_oke_work_requests' indicates listing/querying OKE (Oracle Kubernetes Engine) work requests. The 'list' verb and absence of mutation language suggest a read operation.
Attacks that exploit this kind of access
list_oke_work_requests. It is categorised as a Read tool in the OCI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OCI MCP Server MCP server in PolicyLayer and add a rule for list_oke_work_requests: 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 OCI MCP Server. Nothing to install.
list_oke_work_requests 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_oke_work_requests 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_oke_work_requests. 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_oke_work_requests is provided by the OCI MCP Server MCP server (jopsis/mcp-server-oci). 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 →