Low Risk

kg_get_project_state

Provides a comprehensive overview of a project

How to control kg_get_project_state ↓

What kg_get_project_state does on Personal Kg

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

Low Risk

Why kg_get_project_state needs a policy

This is a read-only tool that retrieves project state data. It has no side effects, does not modify data, execute commands, delete resources, or commit financial obligations. The blast radius of misuse is minimal—an agent could access project information it shouldn't see, but cannot alter system state or trigger external operations.

From the tool's definition Tool name 'kg_get_project_state' and description 'Provides a comprehensive overview of a project' indicate a retrieval operation that queries and returns project state information without modification.

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

How to control kg_get_project_state

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

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

kg_get_project_state 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 Personal Kg — 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 kg_get_project_state

What does the kg_get_project_state tool do? +

Provides a comprehensive overview of a project. It is categorised as a Read tool in the Personal Kg MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on kg_get_project_state? +

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

What risk level is kg_get_project_state? +

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

Can I rate-limit kg_get_project_state? +

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

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

kg_get_project_state is provided by the Personal Kg MCP server (tomschell/personal-kg-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Personal Kg tool call.

Start from Personal Kg, 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.

18 Personal Kg 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.