Report an issue, feature request, or success story for sncro. IMPORTANT: ALWAYS ask the user before submitting ANY feedback. Show them exactly what you plan to send and get explicit approval. Never submit feedback without the user's knowledge and consent. For ALL categories: - Draft the text and ...
Part of the Sncro server.
Free to start. No card required.
AI agents use report_issue to create or modify resources in Sncro. 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 report_issue repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Sncro.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"report_issue": {
"limits": [
{
"counter": "report_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Sncro policy for all 12 tools.
These attack patterns abuse exactly the kind of access report_issue gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Report an issue, feature request, or success story for sncro. IMPORTANT: ALWAYS ask the user before submitting ANY feedback. Show them exactly what you plan to send and get explicit approval. Never submit feedback without the user's knowledge and consent. For ALL categories: - Draft the text and show it to the user BEFORE submitting - Wait for explicit approval — do NOT submit until they confirm - Keep descriptions GENERAL — no proprietary code, no internal project names, no sensitive data For SUCCESS STORIES (category: success_story): - These WILL be displayed publicly on sncro.net - Ask: "Mind if I share that as a sncro success story?" - Focus on what sncro did, not what the project is Args: project_key: The project key from CLAUDE.md category: One of: bug, feature_request, usability, documentation, success_story description: Clear description of the issue, suggestion, or success story git_user: Your git username. It is categorised as a Write tool in the Sncro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sncro MCP server in PolicyLayer and add a rule for report_issue: 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 Sncro. Nothing to install.
report_issue 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 report_issue 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 report_issue. 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.
report_issue is provided by the Sncro MCP server (https://relay.sncro.net/tools/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 12 Sncro tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.