Preview a temporary response safely
Preview a finite WordPress-layer policy, verify its scope, and keep a clear way to disable it before considering active enforcement.
For Free 1.2.7 and Pro 1.2.7. Check the download page for available versions and requirements. Verify representative workflows on staging before use.
On this page
You will be able to explain what the policy can match, when it expires and how to revoke or disable it.
Logged.ai → Requests → Findings; Response → Manual policies
Available in Free and Pro with the relevant request and response permissions. Start from an eligible retained observation on your own site. The public demo allows browsing only; it cannot activate policies.
Have recovery ready first
Keep server-level access and a person who can use it available before activating a response. A WordPress admin session alone is not a recovery plan. Read the recovery steps below before proceeding.
- From the observation, choose Preview temporary policy and a finite duration. If the action is unavailable, read the stated evidence or permission requirement instead of bypassing it.
- Read the exact site, path or reviewed-source conditions, eligible GET/HEAD methods, expiry and matcher examples. Inspect any exact-path exceptions.
- Keep observation-only while assessing scope. This mode records observation without denying a request. Check ordinary site paths that could share the target conditions.
- Only if the scope is justified, choose active mode and acknowledge the effect and recovery procedure. Activation also enables local response for valid existing policies, so review those policies too.
- Open Response → Manual policies to confirm the saved mode and policy. Choose Revoke when that policy is no longer needed.
For one policy, use Revoke in Manual policies. To stop local response when the dashboard cannot be used, a server operator can run this from the correct WordPress installation, replacing the example site URL:
wp logged-ai response disable --url=https://your-site.exampleAlternatively, the operator can add the following to wp-config.php before WordPress loads:
define('LOGGED_AI_DISABLE_RESPONSE', true);There is no public recovery URL or bypass cookie. After regaining access, inspect the saved response mode and policies before making further changes.
Expiry and exceptions
Expiry is checked on eligible requests without waiting for cron. An exact-path exception applies only to its selected policy; it neither grants WordPress access nor overrides another policy.
Keep query conditions unambiguous
Query-condition policies respect the host’s PHP query separators and input-variable limit. When those rules make the requested match ambiguous or truncate the necessary input, Logged.ai declines that manual-policy match. Preview the exact intended path and condition on your host before enabling a response; this is not a general request firewall.
This is a temporary WordPress-layer control. Earlier code may already have run, and requests answered upstream may never reach it. It does not replace an upstream firewall. Ambiguous or encoded input can remain observation-only.
Exact-source targeting can affect unrelated users behind the same network and ordinary login, checkout or API reads. A narrow-looking address is not necessarily one person.
- The saved site, target, mode and expiry match the reviewed preview.
- Any exceptions are deliberate and attached to the intended policy.
- You have checked existing valid policies before enabling local response.
- Ordinary access is still usable and the recovery operator knows how to disable response.
If a preview does not match your intent, leave it unsaved and return to the underlying finding. More uncertain evidence is a reason to investigate, not to broaden a policy.
This guide covers Logged.ai Free 1.2.7 and Pro 1.2.7. Check available versions and package requirements, and verify representative workflows on staging before updating your main site.
Get help with your next step.