Search for assets in the Picsha AI platform using vector or standard keyword search. Note: If your agent instance is sandboxed to a specific user via environment variables, this search will ONLY return assets owned by that specific user. You are securely retrieving their contextual assets.
AI agents call search_assets to retrieve information from Picsha AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves data (assets) based on search parameters with no side effects or data modification. The sandboxing to specific users via environment variables is a security feature that limits the scope of retrieved data, but does not change the fundamental read-only nature of the operation. Blast radius is minimal as it only returns existing data the user already owns.
From the tool's definition Tool description explicitly states it 'Search[es] for assets' and 'retriev[es] their contextual assets' with no modification or deletion capability mentioned. The function performs a query-like operation returning search results.
Attacks that exploit this kind of access
Search for assets in the Picsha AI platform using vector or standard keyword search. Note: If your agent instance is sandboxed to a specific user via environment variables, this search will ONLY return assets owned by that specific user. You are securely retrieving their contextual assets. It is categorised as a Read tool in the Picsha AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Picsha AI MCP Server MCP server in PolicyLayer and add a rule for search_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.
search_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 search_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 search_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.
search_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 →