AI agents use write_tests_tool to create or update resources in FastMCP Boilerplate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FastMCP Boilerplate environment.
This tool creates new test files/content (a reversible write operation). It does not execute code in production, delete anything, move money, or retrieve data without side effects. While code generation tools could theoretically be misused, generating unit tests is a benign write operation with low blast radius—test code is typically sandbox-isolated and non-destructive.
From the tool's definition Tool description states it will "Generate unit tests for the given code." The verb 'Generate' combined with creating new test artifacts constitutes data creation rather than reading, executing arbitrary operations, or deleting data.
Documented attack patterns abuse exactly the kind of access write_tests_tool gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and FastMCP Boilerplate, and nothing reaches the server without passing your rules. This is the rule we recommend for write_tests_tool:
{
"version": "1",
"default": "deny",
"tools": {
"write_tests_tool": {
"limits": [
{
"counter": "write_tests_tool_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}write_tests_tool stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate unit tests for the given code. It is categorised as a Write tool in the FastMCP Boilerplate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FastMCP Boilerplate MCP server in PolicyLayer and add a rule for write_tests_tool: 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 FastMCP Boilerplate. Nothing to install.
write_tests_tool 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 write_tests_tool 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 write_tests_tool. 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.
write_tests_tool is provided by the FastMCP Boilerplate MCP server (rainer85ah/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from FastMCP Boilerplate, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
16 FastMCP Boilerplate tools catalogued and risk-classified — across an index of 43,000+ MCP servers.