Get app info by app shortcut on PGYER
AI agents call get-app-info-by-shortcut to retrieve information from PGYER MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves app metadata by shortcut identifier. It performs a lookup operation returning app information without creating, modifying, deleting, or executing any actions. This is a straightforward read operation with minimal risk—the worst case is information disclosure of already-public app metadata.
From the tool's definition Tool name 'get-app-info-by-shortcut' and description 'Get app info by app shortcut on PGYER' indicate retrieval of existing app information with no modification or side effects.
Attacks that exploit this kind of access
Get app info by app shortcut on PGYER. It is categorised as a Read tool in the PGYER MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PGYER MCP Server MCP server in PolicyLayer and add a rule for get-app-info-by-shortcut: 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 PGYER MCP Server. Nothing to install.
get-app-info-by-shortcut 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 get-app-info-by-shortcut 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 get-app-info-by-shortcut. 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.
get-app-info-by-shortcut is provided by the PGYER MCP Server MCP server (pgyer/pgyer-mcp-server). 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 →