Low Risk

get_metadata

get_metadata

How to control get_metadata ↓

What get_metadata does on Street View MCP

AI agents call get_metadata to retrieve information from Street View MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_metadata needs a policy

The tool name 'get_metadata' indicates a retrieval operation with no side effects. Even though the description is empty (lowering confidence slightly), metadata queries are inherently non-destructive and non-modifying. Within the Street View context, this likely retrieves image metadata such as coordinates, dates, or properties—all read-only operations.

From the tool's definition Tool name 'get_metadata' and context of Street View MCP server suggests retrieval of metadata (likely image properties, location info, or image attributes).

Documented attack patterns abuse exactly the kind of access get_metadata gives an agent:

How to control get_metadata

PolicyLayer is an MCP gateway — it sits between your AI agents and Street View MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_metadata:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_metadata": {}
  }
}

get_metadata is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Street View MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_metadata

What does the get_metadata tool do? +

get_metadata. It is categorised as a Read tool in the Street View MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_metadata? +

Register the Street View MCP server in PolicyLayer and add a rule for get_metadata: 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 Street View MCP. Nothing to install.

What risk level is get_metadata? +

get_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_metadata? +

Yes. Add a rate_limit block to the get_metadata 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.

How do I block get_metadata completely? +

Set action: deny in the PolicyLayer policy for get_metadata. 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.

What MCP server provides get_metadata? +

get_metadata is provided by the Street View MCP server (vlad-ds/street-view-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Street View MCP tool call.

Start from Street View MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

4 Street View MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.