Generate sample data for a template with all required fields filled
AI agents use generate_sample_data to create or update resources in docxtpl MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your docxtpl MCP Server environment.
This tool creates sample/test data programmatically to populate template fields. While it modifies state by adding new data, the data is ephemeral sample content not critical to production systems, and the operation is reversible (samples can be discarded).
From the tool's definition Tool description states "Generate sample data for a template" which creates new data content. The verb "generate" combined with "sample data" indicates data creation/modification rather than retrieval or destruction.
Attacks that exploit this kind of access
Generate sample data for a template with all required fields filled. It is categorised as a Write tool in the docxtpl MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the docxtpl MCP Server MCP server in PolicyLayer and add a rule for generate_sample_data: 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 docxtpl MCP Server. Nothing to install.
generate_sample_data 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 generate_sample_data 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 generate_sample_data. 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.
generate_sample_data is provided by the docxtpl MCP Server MCP server (z1w2r3/doc-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 →