Search the Aesthetics Wiki for pages matching a query.
AI agents call search_aesthetic to retrieve information from Aesthetics Wiki without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data from a knowledge base without modifying, deleting, or executing any operations. It has no side effects and poses minimal security risk. Misuse would be limited to searching for information an AI might not otherwise access, but no data is changed or operations triggered.
From the tool's definition Tool name and description indicate search functionality: 'Search the Aesthetics Wiki for pages matching a query.' Sibling tools like 'get_aesthetic', 'get_aesthetic_images', 'list_related', and 'random_aesthetic' all suggest read-only retrieval operations.
Attacks that exploit this kind of access
Search the Aesthetics Wiki for pages matching a query. It is categorised as a Read tool in the Aesthetics Wiki MCP Server, which means it retrieves data without modifying state.
Register the Aesthetics Wiki MCP server in PolicyLayer and add a rule for search_aesthetic: 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 Aesthetics Wiki. Nothing to install.
search_aesthetic 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_aesthetic 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_aesthetic. 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_aesthetic is provided by the Aesthetics Wiki MCP server (leonardoca1/aesthetics-wiki-mcp). 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 →