Manage PowerPages WebAPI configurations and table permissions. Add/remove WebAPI access for tables, configure table permissions, and check configuration status for PowerPages portals.
AI agents use manage_powerpages_webapi_config to create or update resources in Dataverse MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dataverse MCP Server environment.
This tool modifies security and access control configurations for PowerPages portals by adding/removing WebAPI access and configuring table permissions. While these are reversible (permissions can be re-added or reconfigured), they directly impact data exposure and portal functionality.
From the tool's definition Tool performs 'Add/remove WebAPI access for tables' and 'configure table permissions' — these are configuration modifications that create or alter access control settings in Dataverse PowerPages portals.
Documented attack patterns abuse exactly the kind of access manage_powerpages_webapi_config gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Dataverse MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage_powerpages_webapi_config:
{
"version": "1",
"default": "deny",
"tools": {
"manage_powerpages_webapi_config": {
"limits": [
{
"counter": "manage_powerpages_webapi_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} manage_powerpages_webapi_config stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Manage PowerPages WebAPI configurations and table permissions. Add/remove WebAPI access for tables, configure table permissions, and check configuration status for PowerPages portals. It is categorised as a Write tool in the Dataverse MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for manage_powerpages_webapi_config: 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 Dataverse MCP Server. Nothing to install.
manage_powerpages_webapi_config is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the manage_powerpages_webapi_config 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 manage_powerpages_webapi_config. 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.
manage_powerpages_webapi_config is provided by the Dataverse MCP Server MCP server (mwhesse/dataverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Dataverse MCP Server, 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.
71 Dataverse MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.