Generate mock data for a table using AI and insert it into the database. Automatically handles foreign key references and type conversions.
Part of the Zion MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use create_and_save_mock_data_recursively to create or modify resources in Zion. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call create_and_save_mock_data_recursively repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Zion.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
create_and_save_mock_data_recursively:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Zion policy for all 7 tools.
Agents calling write-class tools like create_and_save_mock_data_recursively have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Generate mock data for a table using AI and insert it into the database. Automatically handles foreign key references and type conversions.. It is categorised as a Write tool in the Zion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for create_and_save_mock_data_recursively. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Zion MCP server.
create_and_save_mock_data_recursively 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 create_and_save_mock_data_recursively rule in your Intercept 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 Intercept policy for create_and_save_mock_data_recursively. 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.
create_and_save_mock_data_recursively is provided by the Zion MCP server (zion-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.