get_oke_work_request
AI agents call get_oke_work_request 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 'get_' prefix strongly indicates a read-only retrieval operation with no side effects. While the description is empty, the naming convention and context of sibling read-only tools provide high confidence this retrieves work request status data from OCI's Kubernetes service. The blast radius of misuse is minimal—an agent could only view operational status information, not modify or delete resources.
From the tool's definition Tool name 'get_oke_work_request' follows the 'get_' pattern, consistent with sibling tools like 'get_alarm', 'get_autonomous_database', 'get_bucket', 'get_budget', 'get_cost_by_compartment' which are all retrieval operations.
Attacks that exploit this kind of access
get_oke_work_request. 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 get_oke_work_request: 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.
get_oke_work_request 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_oke_work_request 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_oke_work_request. 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_oke_work_request 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 →