update_item_metadata · SDOF Knowledge Base MCP

WHAT IT DOES

What update_item_metadata does on SDOF Knowledge Base

AI agents use update_item_metadata to create or update resources in SDOF Knowledge Base — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SDOF Knowledge Base environment.

WHY IT NEEDS A POLICY

Why update_item_metadata needs a policy

This is a Write operation because it creates or modifies data reversibly. It updates metadata on stored items without destructive intent or code execution. Severity is medium because metadata updates could affect system behavior or knowledge retrieval if tampered with by a misaligned agent, but the impact is localized to item metadata rather than core data deletion or financial impact.

From the tool's definition 'Updates metadata for a specified ConPort item' — this operation modifies data (metadata fields) on existing items in the knowledge base. The action is reversible (metadata can be re-updated), and does not delete or execute code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_item_metadata Rate-limited

update_item_metadata 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_item_metadata": {
      "limits": [
        {
          "counter": "update_item_metadata_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 SDOF Knowledge Base, so you can run agents against it safely.

FAQ

Questions about update_item_metadata

What does the update_item_metadata tool do? +

Updates metadata for a specified ConPort item (e.g., decision, system_pattern, custom_data, progress_entry). It is categorised as a Write tool in the SDOF Knowledge Base 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_item_metadata? +

Register the SDOF Knowledge Base MCP server in PolicyLayer and add a rule for update_item_metadata: 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 SDOF Knowledge Base. Nothing to install.

What risk level is update_item_metadata? +

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

Can I rate-limit update_item_metadata? +

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

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

update_item_metadata is provided by the SDOF Knowledge Base MCP server (tgf-between-your-legs/sdof-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.