# AgentPMT-Report-Tool-Issue

Report an issue with a tool to the AgentPMT team.

Agent View of the PolicyLayer registry record for `AgentPMT-Report-Tool-Issue`. HTML page: https://policylayer.com/tools/agentpmt-agentic-marketplace/agentpmt-report-tool-issue

## Facts

- Tool: `AgentPMT-Report-Tool-Issue`
- Server: AgentPMT - The Marketplace For Autonomous Agents (`agentpmt/agentic-marketplace`) — https://policylayer.com/tools/agentpmt-agentic-marketplace.md
- Homepage: https://github.com/agentpmt/agentic-marketplace
- Risk category: Write (Medium risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 3
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `tool_name` | string | no |  |
| `error_message` | string | no |  |
| `recommended_improvements` | string | no |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "AgentPMT-Report-Tool-Issue",
    "arguments": {}
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches AgentPMT - The Marketplace For Autonomous Agents:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "AgentPMT-Report-Tool-Issue": {
      "limits": [
        {
          "counter": "agentpmt-report-tool-issue_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on AgentPMT - The Marketplace For Autonomous Agents (3)

- `AgentPMT-Tool-Search-and-Execution` — Execute — https://policylayer.com/tools/agentpmt-agentic-marketplace/agentpmt-tool-search-and-execution.md
- `AgentPMT-Workflow-Skills` — Execute — https://policylayer.com/tools/agentpmt-agentic-marketplace/agentpmt-workflow-skills.md
- `AgentPMT-Send-Human-Request` — Other — https://policylayer.com/tools/agentpmt-agentic-marketplace/agentpmt-send-human-request.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=agentpmt-agentic-marketplace · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/agentpmt-agentic-marketplace