List properties for a Sanka object family such as orders, companies, or deals. Use this before creating or updating object records when you need the current property schema. Company billing_cycle and payment_cycle are standard company fields, not a custom-property discovery flow.
AI agents call list_properties to retrieve information from Sanka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural metadata about Sanka object families (orders, companies, deals) to discover available properties and fields. It performs a read-only query operation with no capability to modify, delete, or execute external operations. The intended use case is informational—gathering schema information before other operations. No data is modified, deleted, or executed.
From the tool's definition Tool name 'list_properties' and description explicitly states it 'List properties' and is used to query 'the current property schema' before creating or updating records. This is a schema/metadata retrieval operation with no side effects.
Attacks that exploit this kind of access
List properties for a Sanka object family such as orders, companies, or deals. Use this before creating or updating object records when you need the current property schema. Company billing_cycle and payment_cycle are standard company fields, not a custom-property discovery flow. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_properties: 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 Sanka MCP Server. Nothing to install.
list_properties is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_properties 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.
Set action: deny in the PolicyLayer policy for list_properties. 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.
list_properties is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →