rebuild_metadata_index

WHAT IT DOES

What rebuild_metadata_index does on Trade Surveillance Support MCP Server

AI agents invoke rebuild_metadata_index to trigger actions in Trade Surveillance Support MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why rebuild_metadata_index needs a policy

This tool performs a metadata index rebuild—a system operation that executes/triggers backend processes. While not destructive (index can be rebuilt again) and not directly reading/writing user data, it initiates computational operations that affect the behavior of downstream search and query functions.

From the tool's definition Tool name 'rebuild_metadata_index' combined with server description indicating 'metadata annotations' used for searching code and configs. Rebuilding an index is an operational action that triggers processing/execution of systems.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rebuild_metadata_index Rate-limited

rebuild_metadata_index stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rebuild_metadata_index": {
      "limits": [
        {
          "counter": "rebuild_metadata_index_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about rebuild_metadata_index

What does the rebuild_metadata_index tool do? +

rebuild_metadata_index. It is categorised as a Execute tool in the Trade Surveillance Support MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on rebuild_metadata_index? +

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

What risk level is rebuild_metadata_index? +

rebuild_metadata_index is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit rebuild_metadata_index? +

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

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

rebuild_metadata_index is provided by the Trade Surveillance Support MCP Server MCP server (vic3custodio/mcp_test_2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.