list_assets
AI agents call list_assets to retrieve information from Mattcoatsworth Canva without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, we infer behavior from the tool name and context. 'List' operations retrieve and enumerate data without modification or side effects. The consistent pattern of read-only operations in sibling tools on this Canva API server supports a Read classification. Confidence is moderate (0.75) due to the missing description; a full description would yield higher confidence.
From the tool's definition Tool name is 'list_assets' with an empty description. The prefix 'list' indicates a retrieval operation. Sibling tools on the same server (list_brands, list_designs, list_users, get_asset, get_brand, get_design, get_user) are all read-only data retrieval…
Attacks that exploit this kind of access
list_assets. It is categorised as a Read tool in the Mattcoatsworth Canva MCP Server, which means it retrieves data without modifying state.
Register the Mattcoatsworth Canva MCP server in PolicyLayer and add a rule for list_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 Mattcoatsworth Canva. Nothing to install.
list_assets is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_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 list_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.
list_assets is provided by the Mattcoatsworth Canva MCP server (@iflow-mcp/mattcoatsworth-canva-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 →