Skip to main content
Glama
ThalesGroup

Imperva Cloud WAF MCP Server

Official
by ThalesGroup

get_rules_of_account_tool

Fetch custom rules (rate, security, redirect, rewrite, forward) assigned to sites in an Imperva account.

Instructions

Fetches the custom rules details associated with the sites under the given account. The supported type of rules are: rate rules, security rules, forward rules, redirect rules, rewrite rules

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idYesUnique identifier of the sub-account, if the account in context is the main account associated to the used API_ID this field MUST be empty (Optional)
site_idsNolist of sites IDs, only rules assigned to sites with those IDs will retrieve, if it exists (Optional)
sub_accounts_idsNolist of subaccounts IDs, only rules assigned to sites under those subaccounts will retrieve, if it exists. (Optional)
rules_idsNolist of rules IDs, only rules with those IDs will retrieve, if it exists (Optional)
categoriesNolist of rules categories, only rules with those types will retrieve, if it exists. possible values are "WafOverride","WafOverride","RewriteResponse","SimplifiedRedirect","Security","Rates","Rewrite","Redirect". (Optional)
namesNolist of rules names, only rules with those names will retrieve, if it exists. (Optional)
page_numNo
page_sizeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so description must disclose behavioral traits. It only states the basic purpose and rule types, omitting details on read-only nature, pagination, filtering behavior, auth requirements, or potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two-sentence description is concise and front-loaded with the action and scope. No fluff, though could be slightly more structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema exists, the description does not need to detail return values. However, it lacks mention of pagination and filtering capabilities, which are important for correct usage. Adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 75%, so most parameters are already documented. The description adds minimal value beyond the schema, primarily listing rule types which overlap with the 'categories' parameter description. Baseline score applied.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool fetches custom rules details for sites under an account and lists the supported rule types. It distinguishes from sibling tools which deal with domains, policies, or site details. However, it could be more specific about what 'custom rules details' includes.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description provides no guidance on when to use this tool versus siblings or alternatives. No exclusions or context-specific usage hints are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ThalesGroup/imperva-cloud-WAF-MCP-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server