update_stock_holding · Corpus MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_stock_holding does on Corpus MCP Server

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

WHY IT NEEDS A POLICY

Why update_stock_holding needs a policy

The tool modifies (rather than deletes) existing portfolio data, placing it in the Write category. Severity is high because misuse could alter financial holdings records, potentially causing incorrect portfolio valuations, tax reporting errors, or decision-making based on false data.

From the tool's definition Tool name 'update_stock_holding' and description 'Update an existing stock holding' indicate modification of financial asset records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_stock_holding Rate-limited

update_stock_holding 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": {
    "update_stock_holding": {
      "limits": [
        {
          "counter": "update_stock_holding_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 Corpus MCP Server, so you can run agents against it safely.

FAQ

Questions about update_stock_holding

What does the update_stock_holding tool do? +

Update an existing stock holding. It is categorised as a Write tool in the Corpus 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 update_stock_holding? +

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

What risk level is update_stock_holding? +

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

Can I rate-limit update_stock_holding? +

Yes. Add a rate_limit block to the update_stock_holding 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 update_stock_holding completely? +

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

update_stock_holding is provided by the Corpus MCP Server MCP server (mathankarthik18/corpus-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.