Submit fixed code to earn lollipops! 🍭
AI agents use submit_fixed_code to create or update resources in MCP Pyrefly — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Pyrefly environment.
This is a Write operation because it modifies code reversibly—accepting submissions of corrected code that can be undone or overwritten. It does not delete data (Destructive), execute arbitrary operations (Execute), or move money (Financial).
From the tool's definition 'Submit fixed code' modifies code in a repository or system by accepting and storing corrected versions. The gamification context ('earn lollipops') indicates persistent state changes.
Attacks that exploit this kind of access
Submit fixed code to earn lollipops! 🍭. It is categorised as a Write tool in the MCP Pyrefly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Pyrefly MCP server in PolicyLayer and add a rule for submit_fixed_code: 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 MCP Pyrefly. Nothing to install.
submit_fixed_code 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 submit_fixed_code 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 submit_fixed_code. 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.
submit_fixed_code is provided by the MCP Pyrefly MCP server (kimasplund/mcp-pyrefly). 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 →