Link a source/parent asset to a target/child asset (e.g. variations, derived formats, social crops) with a custom relationship description.
AI agents use link_assets to create or update resources in Picsha AI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Picsha AI MCP Server environment.
This tool creates a relationship/association between two existing assets. It modifies metadata/relational data in the DAM system but does not delete, execute code, or involve finances. It is reversibly a write operation (links can typically be unlinked), hence Write at medium severity since misconfigured links could corrupt asset hierarchy or relationships.
From the tool's definition Link a source/parent asset to a target/child asset...with a custom relationship description
Attacks that exploit this kind of access
Link a source/parent asset to a target/child asset (e.g. variations, derived formats, social crops) with a custom relationship description. It is categorised as a Write tool in the Picsha AI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Picsha AI MCP Server MCP server in PolicyLayer and add a rule for link_assets: 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 Picsha AI MCP Server. Nothing to install.
link_assets 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 link_assets 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 link_assets. 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.
link_assets is provided by the Picsha AI MCP Server MCP server (picsha-ai/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →