AI agents use convert_case to create or update resources in Awesome-MCP-Scaffold — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Awesome-MCP-Scaffold environment.
The tool modifies text content reversibly (case conversion can always be reversed), which places it in the Write category. Severity is low because case conversion has minimal blast radius—the worst outcome is incorrectly formatted text that can be easily corrected.
From the tool's definition Tool name 'convert_case' and description 'Convert text case' indicate the tool transforms text by changing its case (uppercase, lowercase, title case, etc.).
Documented attack patterns abuse exactly the kind of access convert_case gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Awesome-MCP-Scaffold, and nothing reaches the server without passing your rules. This is the rule we recommend for convert_case:
{
"version": "1",
"default": "deny",
"tools": {
"convert_case": {
"limits": [
{
"counter": "convert_case_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}convert_case 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.
Convert text case. It is categorised as a Write tool in the Awesome-MCP-Scaffold MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Awesome-MCP-Scaffold MCP server in PolicyLayer and add a rule for convert_case: 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 Awesome-MCP-Scaffold. Nothing to install.
convert_case 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 convert_case 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 convert_case. 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.
convert_case is provided by the Awesome-MCP-Scaffold MCP server (ww-ai-lab/awesome-mcp-scaffold). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Awesome-MCP-Scaffold, 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.
24 Awesome-MCP-Scaffold tools catalogued and risk-classified — across an index of 43,000+ MCP servers.