Set or update agent metadata key-value pair on Identity Registry
AI agents use set_metadata to create or update resources in Waiaas — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Waiaas environment.
The tool modifies metadata on an Identity Registry, which is a data mutation operation. While not destructive (changes can be reversed), it goes beyond read-only access. Severity is medium rather than high because metadata updates have limited blast radius compared to financial operations or destructive actions on this wallet server.
From the tool's definition Tool description explicitly states 'Set or update agent metadata key-value pair', which are write operations that create or modify data reversibly.
Documented attack patterns abuse exactly the kind of access set_metadata gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Waiaas, and nothing reaches the server without passing your rules. This is the rule we recommend for set_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"set_metadata": {
"limits": [
{
"counter": "set_metadata_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_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.
Set or update agent metadata key-value pair on Identity Registry. It is categorised as a Write tool in the Waiaas MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Waiaas MCP server in PolicyLayer and add a rule for set_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 Waiaas. Nothing to install.
set_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 set_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 set_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.
set_metadata is provided by the Waiaas MCP server (minhoyoo-iotrust/waiaas). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Waiaas, 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.
126 Waiaas tools catalogued and risk-classified — across an index of 43,000+ MCP servers.