Parses a user's standard GitHub Markdown and restructures it into modern,
AI agents use refactor_readme_to_bento to create or update resources in GodProfile MCP Toolkit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GodProfile MCP Toolkit environment.
This tool takes existing README markdown and transforms its structure into a bento-grid layout format. This is a reversible modification operation—the original content remains accessible and the change can be undone by reverting the README file. It does not delete data permanently, execute arbitrary code, or move money, making Write the appropriate category.
From the tool's definition Tool name 'refactor_readme_to_bento' and description 'Parses a user's standard GitHub Markdown and restructures it' indicate the tool modifies and rewrites README content.
Documented attack patterns abuse exactly the kind of access refactor_readme_to_bento gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GodProfile MCP Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for refactor_readme_to_bento:
{
"version": "1",
"default": "deny",
"tools": {
"refactor_readme_to_bento": {
"limits": [
{
"counter": "refactor_readme_to_bento_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}refactor_readme_to_bento 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.
Parses a user's standard GitHub Markdown and restructures it into modern,. It is categorised as a Write tool in the GodProfile MCP Toolkit MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GodProfile MCP Toolkit MCP server in PolicyLayer and add a rule for refactor_readme_to_bento: 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 GodProfile MCP Toolkit. Nothing to install.
refactor_readme_to_bento 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 refactor_readme_to_bento 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 refactor_readme_to_bento. 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.
refactor_readme_to_bento is provided by the GodProfile MCP Toolkit MCP server (luc0-0/godprofile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GodProfile MCP Toolkit, 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 GodProfile MCP Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.