List resources with a specific tag
AI agents call list_resources_by_tag to retrieve information from Payments Developer Portal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only retrieval operation on payment documentation and resources. It filters and returns existing data based on a tag parameter with no side effects. Even in a payments context, documentation access carries minimal risk.
From the tool's definition The tool is named 'list_resources_by_tag' and described as 'List resources with a specific tag'. This is a query/listing operation that retrieves or indexes existing resources without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List resources with a specific tag. It is categorised as a Read tool in the Payments Developer Portal MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Payments Developer Portal MCP Server MCP server in PolicyLayer and add a rule for list_resources_by_tag: 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 Payments Developer Portal MCP Server. Nothing to install.
list_resources_by_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_resources_by_tag 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 list_resources_by_tag. 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.
list_resources_by_tag is provided by the Payments Developer Portal MCP Server MCP server (praveenjoshua23/mcp-portal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →