Add a testimonial/quote section
AI agents use add_testimonial to create or update resources in Noleemits Vision Builder MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Noleemits Vision Builder MCP environment.
This tool creates or adds new content sections (testimonial blocks) to existing pages, which is reversible modification of data. It does not execute arbitrary code, delete content, move financial resources, or perform destructive operations.
From the tool's definition The tool name 'add_testimonial' and description 'Add a testimonial/quote section' indicate creation of new content blocks on a WordPress/Elementor page. This is a write operation that modifies page structure and content.
Attacks that exploit this kind of access
Add a testimonial/quote section. It is categorised as a Write tool in the Noleemits Vision Builder MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Noleemits Vision Builder MCP server in PolicyLayer and add a rule for add_testimonial: 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.
add_testimonial 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 add_testimonial 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 add_testimonial. 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.
add_testimonial 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 →