Update existing metadata documentation for an Elasticsearch index
AI agents use update_index_metadata to create or update resources in Agent Knowledge MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Knowledge MCP environment.
The tool modifies metadata documentation for Elasticsearch indices. This is a Write operation because it creates or modifies data reversibly—metadata can be updated again or reverted. It does not execute arbitrary code (Execute), delete irreversibly (Destructive), move money (Financial), or retrieve data without side effects (Read).
From the tool's definition Tool name 'update_index_metadata' and description 'Update existing metadata documentation' indicate modification of index metadata. This is a reversible change to index configuration/documentation.
Documented attack patterns abuse exactly the kind of access update_index_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Agent Knowledge MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for update_index_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"update_index_metadata": {
"limits": [
{
"counter": "update_index_metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_index_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.
Free to start. No card required.
Update existing metadata documentation for an Elasticsearch index. It is categorised as a Write tool in the Agent Knowledge MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Knowledge MCP server in PolicyLayer and add a rule for update_index_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 Agent Knowledge MCP. Nothing to install.
update_index_metadata is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_index_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.
Set action: deny in the PolicyLayer policy for update_index_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.
update_index_metadata is provided by the Agent Knowledge MCP server (itshare4u/agentknowledgemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Agent Knowledge MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
27 Agent Knowledge MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.