New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

knowledge_base_update

Update an existing knowledge base FAQ

SERVERGhl SOURCE@aiwerk/mcp-server-ghl
Medium RISK CLASS
Category Write
Parameters 33 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiwerk-mcp-server-ghl/knowledge-base-update.md

What knowledge_base_update does on Ghl

AI agents use knowledge_base_update to create or update resources in Ghl, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ghl environment.

ParameterTypeRequiredDescription
id string Yes faq ID as string
answer string Yes faq answer as a string
question string Yes faq question as a string

Parameters from the server's own tool schema.

Why knowledge_base_update is rated Medium

An AI agent can call knowledge_base_update faster than any human can review: one bad instruction and it creates or modifies resources in Ghl by the hundred, each call as confident as the last.

Questions about knowledge_base_update

What does the knowledge_base_update tool do? +

Update an existing knowledge base FAQ. It is categorised as a Write tool in the Ghl MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does knowledge_base_update accept? +

knowledge_base_update accepts 3 parameters: id, answer, question. Required: id, answer, question. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on knowledge_base_update? +

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

What risk level is knowledge_base_update? +

knowledge_base_update is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit knowledge_base_update? +

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

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

knowledge_base_update is provided by the Ghl MCP server (@aiwerk/mcp-server-ghl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Ghl, and thousands of servers like it.

This server

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Ghl's. Pull the full record:

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.