AI agents call get_place_info to retrieve information from Melo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves existing metadata without creating, modifying, deleting, or executing any operations. The returned data is descriptive information about a place. While the placeId and creatorId could theoretically be used as inputs to other tools for malicious purposes, the tool itself performs only a read operation with no side effects or blast radius on its own.
From the tool's definition Tool description states 'Get metadata about the currently open place' and returns only informational fields (name, placeId, creatorId, creatorType, description) with no modification or side effects.
Attacks that exploit this kind of access
Get metadata about the currently open place — name, place ID, creator, game settings. Returns: { name, placeId, creatorId, creatorType, description }. It is categorised as a Read tool in the Melo MCP Server, which means it retrieves data without modifying state.
Register the Melo MCP server in PolicyLayer and add a rule for get_place_info: 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 Melo. Nothing to install.
get_place_info 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_place_info 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_place_info. 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_place_info is provided by the Melo MCP server (yannyhl/linkedsword-mcp). 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 →