AI agents call get_vertex to retrieve information from TG_MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a single vertex from the TigerGraph database by its type and ID. Retrieval operations that do not modify, delete, or execute code fall squarely into the Read category. The operation is limited in blast radius since it only fetches existing data. Severity is low because an AI agent misusing this tool could at worst retrieve sensitive data it shouldn't access, but cannot modify or destroy anything.
From the tool's definition Tool name 'get_vertex' and description 'Retrieve a vertex by type and ID' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
MCP tool: Retrieve a vertex by type and ID. It is categorised as a Read tool in the TG_MCP MCP Server, which means it retrieves data without modifying state.
Register the TG_ MCP server in PolicyLayer and add a rule for get_vertex: 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 TG_MCP. Nothing to install.
get_vertex 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_vertex 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_vertex. 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_vertex is provided by the TG_ MCP server (muzain187/tg_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 →