List available layout patterns (Bento, Masonry, Zigzag, Grid)
AI agents call list_patterns to retrieve information from Noleemits Vision Builder MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a static list of layout pattern options (Bento, Masonry, Zigzag, Grid) available for page design. It performs a read-only lookup with no capability to modify, delete, execute code, or trigger external actions. The blast radius of misuse is minimal—an agent could at worst enumerate patterns repeatedly, causing no harm to data or systems.
From the tool's definition Tool name is 'list_patterns' and description states it 'List[s] available layout patterns' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List available layout patterns (Bento, Masonry, Zigzag, Grid). It is categorised as a Read tool in the Noleemits Vision Builder MCP MCP Server, which means it retrieves data without modifying state.
Register the Noleemits Vision Builder MCP server in PolicyLayer and add a rule for list_patterns: 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 Noleemits Vision Builder MCP. Nothing to install.
list_patterns 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_patterns 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_patterns. 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_patterns is provided by the Noleemits Vision Builder MCP server (noleemits/vision-builder-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 →