tool_with_context · OpenAPI REST MCP Server MCP

WHAT IT DOES

What tool_with_context does on OpenAPI REST MCP Server

AI agents use tool_with_context to create or update resources in OpenAPI REST MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your OpenAPI REST MCP Server environment.

WHY IT NEEDS A POLICY

Why tool_with_context needs a policy

An AI agent can call tool_with_context faster than any human can review — one bad instruction and it creates or modifies resources in OpenAPI REST MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

tool_with_context Rate-limited

tool_with_context stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "tool_with_context": {
      "limits": [
        {
          "counter": "tool_with_context_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches OpenAPI REST MCP Server, so you can run agents against it safely.

FAQ

Questions about tool_with_context

What does the tool_with_context tool do? +

tool_with_context. It is categorised as a Write tool in the OpenAPI REST MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tool_with_context? +

Register the OpenAPI REST MCP Server MCP server in PolicyLayer and add a rule for tool_with_context: 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 OpenAPI REST MCP Server. Nothing to install.

What risk level is tool_with_context? +

tool_with_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit tool_with_context? +

Yes. Add a rate_limit block to the tool_with_context 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.

How do I block tool_with_context completely? +

Set action: deny in the PolicyLayer policy for tool_with_context. 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.

What MCP server provides tool_with_context? +

tool_with_context is provided by the OpenAPI REST MCP Server MCP server (saranazeer27/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

tool_with_context is one line of OpenAPI REST MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →