pg_git_semantic_search

Semantically search the contents of all files in PG-Git. Results are automatically decayed by age so recent code ranks higher.

Server PG-Git (Semantic Memory MCP) kruschdev/pg-git-mcp
Category Read
Risk class Low
Parameters 00 required

What pg_git_semantic_search does on PG-Git (Semantic Memory MCP)

AI agents call pg_git_semantic_search to retrieve information from PG-Git (Semantic Memory MCP) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why pg_git_semantic_search needs a policy

This tool retrieves and ranks data from stored files without creating, modifying, deleting, or executing operations. Semantic search with decay ranking is a read-only analytical operation with minimal blast radius—worst case is returning unexpected search results or information disclosure, not data mutation or external side effects.

From the tool's definition Tool performs semantic search across file contents with time-decay ranking. Description indicates retrieval/query operation ('semantically search') with no modification, deletion, or execution capabilities.

Risk signalsBulk/mass operation — affects multiple targets

Questions about pg_git_semantic_search

What does the pg_git_semantic_search tool do? +

Semantically search the contents of all files in PG-Git. Results are automatically decayed by age so recent code ranks higher. It is categorised as a Read tool in the PG-Git (Semantic Memory MCP) MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_git_semantic_search? +

Register the PG-Git (Semantic Memory MCP) MCP server in PolicyLayer and add a rule for pg_git_semantic_search: 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 PG-Git (Semantic Memory MCP). Nothing to install.

What risk level is pg_git_semantic_search? +

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

Can I rate-limit pg_git_semantic_search? +

Yes. Add a rate_limit block to the pg_git_semantic_search 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 pg_git_semantic_search completely? +

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

pg_git_semantic_search is provided by the PG-Git (Semantic Memory MCP) MCP server (kruschdev/pg-git-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.