Skip to main content
Book a demo

Planhat

Keep Planhat customer records current from wherever you're working.

Book a demo

Tools

10 available tools

Search the tool definitions captured from the MCP server. The live list can vary with version, deployment, and credentials.

10 tools found.

  • Create document

    Tool name: create_document

    Create a new document (page) in Planhat.

  • Create model record

    Tool name: create_model_record

    MODEL: "Company", PARAMETERS: {"name": "Acme Corp", "domain": "acme.com"}

  • Delete model record

    Tool name: delete_model_record

    Delete existing record.

  • Get document

    Tool name: get_document

    Retrieve a document (page) by its ID, including its full content.

  • Get model action parameters

    Tool name: get_model_action_parameters

    Returns field metadata (names, types, required flags) for a data model.

  • Get model record

    Tool name: get_model_record

    Get single record by ID.

  • List model records

    Tool name: list_model_records

    MODEL: "Company", LIMIT: 20

  • Search documents

    Tool name: search_documents

    Search documents (pages) by text.

  • Search records

    Tool name: search_records

    Full-text search across records you can access: matches keywords or phrases against indexed text fields (names, titles, bodies, and other searchable content) on multiple models.

  • Update model record

    Tool name: update_model_record

    Update existing record.

Compatibility

Connect Planhat to the clients your teams already use

27 AI clients can connect to Planhat through Runlayer. Pick one for its setup steps and controls.

CursorVS CodeClaudeClaude CodeClaude CoworkChatGPTWindsurfGooseCodexHermesGumloopRaycastWarpGitHub CopilotGitHub Copilot CLIMicrosoft 365 CopilotGemini CLIZedCline CLIAntigravityOpenCodeCrushGleanLovablePerplexityECAOh My Pi

Why Runlayer

Why connect Planhat through Runlayer?

One approved path

Approve Planhat once and everyone gets it in the AI clients they already use. Runlayer holds the credentials, so nothing sits in client configuration.

Fine-grained policy

Control who can use each server, tool, and resource, and under which runtime conditions.

Runtime security

Scan tool inputs and outputs for prompt injection, credential exposure, PII, and data exfiltration, then alert, mask, or block.

Audit and observability

Trace every request across users, clients, tools, policies, scanner decisions, and downstream systems.

Frequently asked questions