table_manage · Asset Aware MCP: Risk & Policy

WHAT IT DOES

What table_manage does on Asset Aware

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

WHY IT NEEDS A POLICY

Why table_manage needs a policy

With no description provided, classification relies on the tool name and context. 'Manage' typically implies modification or update operations on tables (Create, Update operations). Given that sibling tools include destructive operations (delete_document) and conversions, this tool likely modifies table data within PDF assets rather than merely reading them.

From the tool's definition Tool name 'table_manage' combined with sibling tools showing document conversion and deletion patterns suggest data modification capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

table_manage Rate-limited

table_manage 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": {
    "table_manage": {
      "limits": [
        {
          "counter": "table_manage_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 Asset Aware, so you can run agents against it safely.

FAQ

Questions about table_manage

What does the table_manage tool do? +

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

How do I enforce a policy on table_manage? +

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

What risk level is table_manage? +

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

Can I rate-limit table_manage? +

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

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

table_manage is provided by the Asset Aware MCP server (u9401066/asset-aware-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.