Tell support something went wrong, file a bug, request a feature, or flag a slow query. Zero LLM cost, zero credits. Call this when: - A query_data result looks wrong or misleading (pass the query_id from that response — support uses it to investigate the issue). - You hit a confusing error or th...
Part of the Mrmarket Ai server.
Free to start. No card required.
AI agents use report_issue to create or modify resources in Mrmarket Ai. 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 Mrmarket Ai.
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 Mrmarket Ai policy for all 8 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.
Tell support something went wrong, file a bug, request a feature, or flag a slow query. Zero LLM cost, zero credits. Call this when: - A query_data result looks wrong or misleading (pass the query_id from that response — support uses it to investigate the issue). - You hit a confusing error or the same query keeps failing. - A query took unreasonably long (still pass query_id if available). - You wish mrmarket.ai supported something it currently doesn't. This is the PREFERRED support channel because it auto-links to the query trace; email is slower and requires the user to copy/paste the query_id manually. Categories: - wrong_data → result was incorrect / numbers look off - bug → something crashed or the response was malformed - slow → query took too long or timed out - feature_request → "I wish it could do X" - general → catch-all if none of the above fits. It is categorised as a Write tool in the Mrmarket Ai MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mrmarket Ai 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 Mrmarket Ai. 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 Mrmarket Ai MCP server (https://mcp.mrmarket.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Mrmarket Ai 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.