Update a catalog asset's documentation. - description replaces the existing description (auto-sets status to "draft" if status is null). - ai_suggestion proposes a description for user review (does NOT replace the existing one). - tag_ids replaces all tags (accepts names or UUIDs; auto-creates mi...
Part of the Myriade server.
Free to start. No card required.
AI agents use myriade_update_asset to create or modify resources in Myriade. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call myriade_update_asset repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Myriade.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"myriade_update_asset": {
"limits": [
{
"counter": "myriade_update_asset_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Myriade policy for all 10 tools.
These attack patterns abuse exactly the kind of access myriade_update_asset gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Update a catalog asset's documentation. - description replaces the existing description (auto-sets status to "draft" if status is null). - ai_suggestion proposes a description for user review (does NOT replace the existing one). - tag_ids replaces all tags (accepts names or UUIDs; auto-creates missing tags). - status is "draft" (needs review) or "published". Only use "published" with high confidence.. It is categorised as a Write tool in the Myriade MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Myriade MCP server in PolicyLayer and add a rule for myriade_update_asset: 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 Myriade. Nothing to install.
myriade_update_asset 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 myriade_update_asset 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 myriade_update_asset. 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.
myriade_update_asset is provided by the Myriade MCP server (https://app.myriade.ai/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Myriade tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.