Report a problem with the Partle marketplace API/MCP itself. Authenticated. Prefer OAuth: connect once via the consent flow and the bearer token is attached automatically. Fallback: pass an api_key (prefix pk_, generate at /account). Required OAuth scope: feedback:write. Feedback is attributed to...
Risk signalsHandles credentials or secrets (api_key)
Part of the Partle server.
Free to start. No card required.
AI agents use submit_feedback to create or modify resources in Partle. 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 submit_feedback 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 Partle.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"submit_feedback": {
"limits": [
{
"counter": "submit_feedback_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Partle policy for all 21 tools.
These attack patterns abuse exactly the kind of access submit_feedback 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 a problem with the Partle marketplace API/MCP itself. Authenticated. Prefer OAuth: connect once via the consent flow and the bearer token is attached automatically. Fallback: pass an api_key (prefix pk_, generate at /account). Required OAuth scope: feedback:write. Feedback is attributed to your account so reports are trustworthy and the channel can't be flooded anonymously. Scope — what this is for: - A Partle tool description is unclear or its parameters are surprising. - A Partle response is broken, malformed, or missing fields. - The Partle catalog is missing a category of products you'd expect. - Search relevance is off for a specific class of queries on Partle. Scope — what this is NOT for: - General complaints about tasks Partle isn't designed to do (Partle is a local-marketplace search/listing API — not a news API, an HTML hosting service, a portfolio-rebalancing app, a stock brokerage, or a generic dashboard SaaS). - Venting that an invented API key was rejected (Partle keys must be pk_<hex>; generate one at /account — don't fabricate them). - Asking the maintainers to do work the user requested but you can't do. If you can't fulfil a user request, tell the user — don't submit feedback about it here. Don't loop — each call adds a row and pages the maintainer. Resubmitting the same text within 24h is de-duplicated (returns the existing id). Args: feedback: Freeform text up to 5000 characters. Be specific — name the tool, the input that was confusing, and what you expected. api_key: Legacy/fallback auth. Omit when using OAuth. Returns: {"id": int, "message": "Thanks for the feedback!"} on success, or {"error": ...} on auth, rate-limit, or validation failure.. It is categorised as a Write tool in the Partle MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Partle MCP server in PolicyLayer and add a rule for submit_feedback: 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 Partle. Nothing to install.
submit_feedback 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_feedback 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_feedback. 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_feedback is provided by the Partle MCP server (https://partle.rubenayla.xyz/mcp/). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 21 Partle 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.