AgentPMT-Report-Tool-Issue
Report an issue with a tool to the AgentPMT team.
This record as markdown: /tools/agentpmt-agentic-marketplace/agentpmt-report-tool-issue.md
What AgentPMT-Report-Tool-Issue does on AgentPMT - The Marketplace For Autonomous Agents
AI agents use AgentPMT-Report-Tool-Issue to create or update resources in AgentPMT - The Marketplace For Autonomous Agents, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AgentPMT - The Marketplace For Autonomous Agents environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
tool_name | string | — | |
error_message | string | — | |
recommended_improvements | string | — |
Parameters from the server's own tool schema.
Why AgentPMT-Report-Tool-Issue is rated Medium
Reporting an issue is fundamentally a write operation—it submits information to be recorded by the AgentPMT team. It does not execute code or commands, delete data, move money, or perform irreversible actions. The severity is low because submitting a benign issue report carries minimal risk even if misused by an AI agent; the worst outcome would be noise or spam in the issue tracker.
From the tool's definition Tool name 'Report-Tool-Issue' and description indicate the tool creates or submits a new issue report to the AgentPMT team. This is a write operation that reversibly creates data (an issue record) without executing external operations or deleting data.
Attacks that exploit this kind of access
The rule that runs AgentPMT-Report-Tool-Issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AgentPMT - The Marketplace For Autonomous Agents, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For AgentPMT-Report-Tool-Issue, this is the rule to start with:
AgentPMT-Report-Tool-Issue 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AgentPMT - The Marketplace For Autonomous Agents, apply this rule, and every AgentPMT-Report-Tool-Issue call is checked against it from then on.
Questions about AgentPMT-Report-Tool-Issue
Report an issue with a tool to the AgentPMT team. It is categorised as a Write tool in the AgentPMT - The Marketplace For Autonomous Agents MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
AgentPMT-Report-Tool-Issue accepts 3 parameters: tool_name, error_message, recommended_improvements. The full parameter table on this page comes from the server's own tool schema.
Register the AgentPMT - The Marketplace For Autonomous Agents MCP server in PolicyLayer and add a rule for AgentPMT-Report-Tool-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 AgentPMT - The Marketplace For Autonomous Agents. Nothing to install.
AgentPMT-Report-Tool-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 AgentPMT-Report-Tool-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 AgentPMT-Report-Tool-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.
AgentPMT-Report-Tool-Issue is provided by the AgentPMT - The Marketplace For Autonomous Agents MCP server (agentpmt/agentic-marketplace). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AgentPMT - The Marketplace For Autonomous Agents, and thousands of servers like it.
Across the catalogue